Secondly, will it work. I don't mean "kinda work" but I mean over time all the way and is the abstraction flexible and stable enough to prevent VC++ classwizard syndrome (haven't used since 4.2 or so so I assume it is better). You either use the pretty wizard or you don't. Once you change something...the pretty wizard breaks. Then you have to know what it was doing. JSF looks rigid and leaky. It will be interesting to see if it holds up.
On a latter note, I'm not sure the strict VBish development jobs are going to be domestic. I'm not even sure that is bad. I've felt pressure to become a better developer, maybe that�s good economically speaking. -Andy -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. From: Thomas L Roche <[EMAIL PROTECTED]> Reply-To: "Research Triangle Java User's Group mailing list."<[EMAIL PROTECTED]> Date: Wed, 17 Dec 2003 15:20:53 -0500 To: [EMAIL PROTECTED] Subject: [Juglist] Re: JSF Opinion "Andrew C. Oliver" Mon, 15 Dec 2003 20:16:37 -0500 > [JSF] isn't really going to make web programming easier, it will > just tie you to certain folks' tools (as a capture the client take > the server strategy). In my view, JSF doesn't make anyone's life > easier but the tool vendor. True that, but your conclusion is false. Yes, JSF is too complex/ unwieldy for the commandline/texteditor user. But (whether you like it or not :-) there are a lotta IDE users out there (and less-skilled users at that). In fact, one of the attacks the M$ camp has long made on Java is like "I can go into VS and quickly whack up an ASP page--you can't do that." Tightly coupled frameworks and tooling work for entry-level/low-chops users and Model1 tasks: that's the M$ market. So why not have a Java solution for that space? If you find you need a Model2 solution, use SFIL, or equivalent Faces integration foo for <your web framework here> (is there an equivalent for Tapestry), couple your V to a more robust MC, and "migrate up." Just because it doesn't work for you doesn't mean it doesn't work :-) The question should instead be, does the tooling, which is JSF's raison d'etre, help anyone do anything they wanna do? _______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org _______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
