EE Java has always included some crap, always will. It's evolving constantly for sure. Oracle has proven that this is their intent to keep making it better. They are doing this for 1 reason, because no matter how you break it down all this truely means to them is more Oracle DB licences (which are far from cheap), so they are gonna grow their bottom line.
I know people who 2 months ago finished building a very cool enterprise application with Play, so it works. They are not stupid, One of them invented the original Facebook at Stanford years and years before Zuk got in to Harvard. The only difference was that at Stanford, the Dean decided that was an intrusion of privacy and said no that's illegal here and shut them down. And they know all about Tapestry (up to the final refined 4 version) have used it to build rock solid fancy enterprise apps. But they decided to use Play. So clearly in my eyes, Play has some merits. Conclusion: Java EE is never going away, it's just gonna get better, even more of the stupid excess fat will be refactored or totally abandoned. Servlets for sure are never getting dumped because they just flat out work for anything, and they are evolving right along with the rest of the EE. I would say this book that you are reading is fully biased. Most Technical books are in some way biased. I'm certain there is or shortly will be half a dozen other books that aren't as biased. Maybe some day I'll consider reading one of those. Don't get sucked into using something just cus it's new and does a few clever things. It has no real track record and odds are it's never gonna get a big enough user base to allow it survive and evolve. If you want to jump out of the Java boat completely, go learn Python and a couple of their libraries back to front. Transmission Ending. Pausing Rant Nuerons til later. Have a good 1 Happy Hunting Jon On Fri, May 4, 2012 at 9:18 AM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Fri, 04 May 2012 10:57:57 -0300, Vladimir Bauer <vba...@slb.com> wrote: > > Is it really anything based on servlet api, Tapestry for example, is a >> dying technology? >> > > By the way, what does the death or dying of a technology is? I'd say it's > the same as with natural languages: they die when nobody use them anymore. > Is there new web apps being written on the top of the Servlet API directly > or indirectly? Yeeeeeeeeeeeeeeeeeeeeeeeeeeeee**eeeeeeeeeeeeeeeeeeeees. Is > it dying, nooooooooooooooooooooooooooo. :) Tapestry is dying? No. We see > new people posting in the mailing list in a rate I've never seen before. We > even hear news of Tapestry being taught in universities. > > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
