Ted Husted wrote: >... marketshare is not the point of the exercise. > (I wrote this reply, then read Paul B's parallel reply ... I'm definitely thinking along a different track here ... I don't mind the branding issue) While I accept that Ted's comment was placed in the context of Apache project management, I want to add a minor point on a different tack. (Not that my opinion is worth much, but what the hell ... ) Market share of Struts vs JSF (or of j2ee vs .nut, etc etc) is of paramount importance to me as a low-end developer. There are 2 reasons for this. 1/ Market share of a technology leads to more employers looking for that skill. More employers looking for a skill that I am cultivating leads to me being able to get a decent job more easily. Getting a better job pays for food, petrol and mortgage. That *is* a big deal to me. Maybe some people are rolling in lolly and can dictate terms, but not me. I read the job ads as a practice, so that I can know what skills employers in my area are typically buying, both at a time and as a trend, and Struts shows up in the grab bag of employers skill lists about 5x to 10x more than JSF. (I don't think that I've seen Shale in a single job ad here yet.) Maybe that's a local thing. I don't know, I don't read international job ads, because I won't be working interstate let alone internationally. 2/ Market share leads to more developers being skilled up in that technology, so if I code an app for an employer in a well-established with-a-future technology, then I am being quite responsible towards them in their future needs for support and continuity of skills on that app. If I just go with the pinnnacle technology, and developers who understand it are scarce (or aren't willing to work in it!), how is that being responsible towards my employer? How Apache teams manage projects, and how the teams rationalize the continuity and interest in projects is an entirely different matter, but a technology's track record and projected market share over the next 5 years is really crucial to my choices as a garden-variety coder, both for my own and my employers benefit. Remember, I'm not trying to undermine anything that anyone else has said, just adding my low-rung-on-the-ladder perspective.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
