> "Davi Cesar Martins Nascimento" <[EMAIL PROTECTED]> > 09/25/2007 03:08 PM > > The questions are:
(here's the gosple according to me: other may well jump in their own views of history) > why it is dead ECS is not dead, just in a deep, deep sleep ;-) it's in deep sleep maintenance mode: once or twice a year someone finds a bug in a production system and creates a patch. some time later, hopefully someone creates a patch. so, the question is: how did it end this way? ECS is one of the aboriginal jakarta sub-projects. it was in java.apache.org in the days of jserv. it's old. ECS 1 is completed. it's gone just about as far as it's architecture can (as far as the original developers could see, anyway). ECS 2 exists in various forms but the community found new and different ways to do the things they wanted to use ECS2 for. some people went away and created members of the first generation of web application framework. i moved onto xml processing libraries (and the commons). apache uses the rule of three: a projects needs three interested developers to be viable. people drifted off to new projects and ECS slept. it's slept for around half a decade now. > and why it should be dead? it only needs to remain dead until there is a viable community that can find new uses for it in terms of evolution, it's generation zero it predates web application frameworks. most modern (forth generation) frameworks offer so much more functionality to web developers. it predates xml-relational mappers. most modern (third generation) xml-relational mappers offer so much more functionality. of course, progress comes at a price. in comparison, ECS is very reliable and very easy to learn. it's also possible to enforce standards much better. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
