This post originated from an RSS feed registered with Java Buzz
by dion.
Original Post: The need for a common Java stack
Feed Title: techno.blog(Dion)
Feed URL: http://feeds.feedburner.com/dion
Feed Description: blogging about life the universe and everything tech
This is sorely needed in the opensource world, and in no other software arena more than Java.
In general, Java folk are 'engineers'. We like to try the latest and greatest. One project may be Tapestry/Pico/Kodo JDO/Ant and the next WebWork/Spring/Hibernate/Maven. We jump and leap between similar, and very disimilar worlds.
This can seem cool, and flexibility and choice is a pro for Java. But, imagine if you are running a huge company, and your large IT team is running around in this manner.
Now the Java platform becomes a burden as you can't jump between projects easily, education becomes a nightmare, as well as reuse.
The Stack
This is where the need for a common stack comes in. As a CIO of BloodyHuge Inc. I want to enable some flexibility, but within the guidelines of a stack.
Wouldn't it be nice to have a development team start a project and:
Know the technology inside and out (past projects, and good training)
Know the lay of the land for the project (shared dir structure, build goals, etc)
Have helpful code to gen some work (a la Rails)
We need common stacks to do this.
When I saw the SpikeSource announcement and the large amount of technologies in their 'stack', I thought it was missing something. As a company I don't just want to know that technology a thru z is 'certified' from a company, or that they offer support.
They want help. They want you to work with their engineers to choose a common stack that has everything setup from the beginning.
When I look at SourceLabs and their AMP Stack, I think they may have gotten it... although I don't see their Java stack yet.
Previous Topic
