Dakota Jack on 10/09/05 07:09, wrote:


I would strongly suggest you consider the Spring alternative which is
highly unlikely to change in fundamentals for a very long time.


I would argue that technology is shifting to RiA (Ajax, Laszlo, JDNC), so a static framework (if Spring is statick, I would not know, I know they have a Swing project) is not futuristic.

But to the topic... :
In some organizations managers decide what the tech. stack is for them. My theory is that they read PC Week and pick some story like IBM EJB or MS Access, usualy they use logic like: We paid a lot of money for this, this will be good + we paid a lot of money for support, so we know we won't make a mistake. Lets use some inovative design... like push. Use Notes for mail client, and lots of virus scanners and sofware change managment on each PC to improve productivity. Then they direct people to support "company decission" and find ways to use the tech. Of course, sinc tech is expensive, their people are not best paid. Lets call this tech 1st orgnaization. Ex: "We are an IBM shop".

Other organizations let exerienced developers pick an effiective tech stack, based on the business requirments and the business problem. Ex: "We are a business shop".

Of course, mostly there are shades of gray.
I hope to mostly work in the 2nd type of orgnization and .... I spend some time monitoring good tech stacks: Faclets, JDNC, CoR, iBatis, Groovy, Fedora, large MonitorS .... (And sometimes in my mind I put things in a bad tech stack: EJB, Spring(too heavy), ORM, Beans (used to be in good stach untill I used collections more), Notes, DHTML, etc. Your list could be different.

I think Ted is one of people that articulated that in different organizations in different situations one picks an eviroment friendly tech stack, or words to that effect. In order for developers to belive in their tools for one.


.V


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to