> To be sure, there *are* some cool things in S2. What I for one don't > see, and I've heard a similar feeling expressed by many as recently as > at The Ajax Experience earlier this month, is a clear, coherent vision > of how S2 lets me develop these so-called Web 2.0 applications better > than any other framework. What is there in S2 to truly excite Web 2.0 > developers in S2 as compared to other frameworks? That to me is the > fundamental question to be answered, and the fundamental reason S2 > doesn't have the uptake many feel it should. I hesitate to put it > this way because it seems potentially unfair, but I'll say it anyway: > it's almost like S2 is standing on the sidelines while the web > development world moves in a fundamentally different direction, and S2 > isn't keeping up as well as it needs to in order to be the success S1 > was. I would agree to this. I would also suggest that for all the core team (for me at least) there is limited time to commit to the project, and unclear feature direction. Regular releases come not only from a smooth release process, but also having enough new feature and bugs resolves to warrant it :-) With limited time to devote to a project, having cohesion on the features being worked on, and having multiple developers work on them to completion, seems like a better alternative than having everyone work on their "pet" feature, whenever they have time (that exponential decreases).
Just my thoughts... /Ian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
