By scottdelap
via infoq.com
Published: Apr 30 2008 / 01:16
SpringSource has today launched the SpringSource Application Platform, a new application server that harnesses the power of Spring, OSGi and Apache Tomcat technologies to create a complete enterprise application stack, including both a deployment platform and a uniquely productive programming model - without Java EE.
Comments
dzonelurker replied ago:
"an application server built on Spring, OSGi, and Apache Tomcat"
LoL Tomcat. They haven't even built their own Servlet container for their "Application Server".
"SpringSource Application Platform is not a Java EE application server ... The SpringSource Application Platform has been designed from the ground up to instead focus directly on supporting the widely used Spring Portfolio".
Proprietary APIs and vendor lock-in instead of the Standardized EE platform? No, thanks!
villane replied ago:
So what? Why should they build a new servlet container if there are several available. For example, if I'm not mistaken, BEA is using Jetty in future servers.
There seems to be some proprietary stuff in there, but OSGi is not proprietary. By now it's pretty much a de facto standard. And so is Spring. Sometimes having a standard just for the sake of it isn't the best solution, as Spring has already proved.
TroubleX replied ago:
"Proprietary APIs and vendor lock-in instead of the Standardized EE platform? No, thanks! "
Wow, I've read some really ignorant, dumb things on comments on teh internets but this has got to take the cake. Do you even know anything at all about the so called "official" JEE standard - owned by Sun btw. It is one of the most bloated, overblown, unfriendly, painful set of application libraries that have ever been shat into existence. And you have the nerve to criticise the Spring team - who have proven time and again that being tied to the "standard" is is more of a lock-in than anything you could possibly do. yeah, sure, it's the official Line - but if you know anything about the history of EJB (which I doubt, you are probably just a .Net WUM) you will know that it was the complexity and horrific experiences borne out of J2EE that Spring sprang from (excuse the pun).
For someone to claim Spring is more of a proprietary lock-in (show me software that DOESN'T lock you in and I'll show you a bullshit artist) over and above the "official" JEE stack simply shows a basic lack of knowledge and if I was to interview you the interview would end very quickly if you uttered such an idiotic statement. Good luck with your "standardised" platform, no doubt Sun will be glad for your support of their proprietary platform.
lifewithryan replied ago:
"show me software that DOESN'T lock you in and I'll show you a bullshit artist"
Just curious on your view on how PHP locks you into anything in particular? Or any one company/server/ etc? Or Perl? Or Python? (not that i know much about Python yet). If anything sounds like .Net WUM its statement like that. Really the .Net world is the only one that, in my mind completely locks you down to anything, and to make a statement like that makes one thing thats the world you're used to.
TroubleX replied ago:
"Just curious on your view on how PHP locks you into anything in particular?"
Well, it locks you in to PHP. Have yo uever had to hack someon;es 1,200 line crappy PHP4 scripts? I can assure you that I have and the clients who are victims of it certainly do feel locked in. (In one case we had to port a PHP/MySQL app to Oracle, and there was no abstraction of the data layer to speak of and turned into a nightmare project - that to me is a case of lock-in. Being locked in is not a technology choice, it's a quality of developement choice).
So, I ask: Why is a decision to use PHP as language any different to choosing a certain IoC container? However, my point was to highlight the remarkable statement that Spring is more of a corporate lock-in than the official JEE stack. An absurd and (imho) ignorant comment.
Voters For This Link (48)
Voters Against This Link (1)