--- Begin Message --- I'd actually like to see a peer to Jakarta for flat out "client-side".. Java GUIs and stuff aren't as crappy as they used to be with new technologies and the falling out of favor of bad technology...
Whether this should be @ apache or a new cli-ache that is not language specific I do not know...
At least part of the growth of the internet is Apache.... a place where these standards get developed, etc.. Unfortunately, the internet is largely computer science coming around full circle.. And it coming around full circle has less to due with client server failing, than a company who couldn't make client-server succeed becoming the dominant undisputed player there, in part due to lack of an Apache in that field. (Coming full circle is a reference to mainframes and dumb terminals...the internet architecture smells like it....a lot)
The maturation of the internet will be to leave the circle and end up somewhere in the middle (achieve balance). We'll have a range of choices (again) from thin (and somewhat crappy, lets face it html forms set things back a few years as far as user interfaces any way you slice it), medium and fat client applications...
Such an organization would help facilitate more rational choices in application design ;-)
Fire away ;-)
-Andy
This issue arises because IMO Jakarta represents, to the Java community in general, the pinacle of achievement. If a project succeeds on Sourceforge, it typically wants to move to Jakarta to finally prove that its 'made it'. Jakarta is that strong a brand.
Clearly there are many things in Jakarta already that are not strictly 'server side'. The Jakarta commons [lang], [io] and [collections] sub sub projects are not tied to the server side for example.
Personally I would prefer to see the 'server-side' reference removed from the Jakarta mission. That of course pushes the question back to you as to why you find that unacceptable?
Stephen
--- End Message ---
