Linked by Eugenia Loli on Fri 28th Jul 2006 18:28 UTC
Thread beginning with comment 147131
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
"Migrating" whole deployments is silly, unless you like nothing but pain. Existing deployments don't just up and go, just slowly phased out while new stuff gets added on; after all, we're still sitting on top of tons of COBOL.
What shifts is the primary development platform, this is the 60%. When ever someone says XYZ has ABC% of the development market, they're usually talking about the space on new development, not what's already there.




Member since:
2005-07-12
You are 100% correct.
I've seen no evidence of Java to .Net migration, in any way, shape, or form.
It's either the company is an all Microsoft shop, or it has a mix and match. Most of the all MS shops go with .Net, with a small amount using Java. And any mix and match house has to go Java, or perhaps RoR, or perhaps LAMP, or anything else that is cross platform.
And yes, the increase in .Net is mostly old VB to .Net migration, or old C++/MFC to C# migration.
When that transition period ends, so will the current growth rate of .Net. It will settle down, with more regular growth rates.