FYI – Windows 7 Surpasses Mac OS X In Terms Of Market Share
Satellite Environment Software on the NetBeans Platform
Ajax: JQuery, GWT or RichFaces
Mark Reinhold on Closures for Java
Public Transportation on the NetBeans Platform
Write Your First Google Wave Robot in Java
A JPEG Encoder for JavaScript 
By dp619
via sdtimes.com
Published: Aug 11 2008 / 14:38
Comments
gregsmith104 replied ago:
I'm glad to hear that Microsoft is concerned about this...I know I am. I began my development career with .NET v1.1 changed mid-project to v2.0 because of the advantage of Generics for my project and am now looking to v3.5, because I missed v3.0. This was over a 4 year period. MS need to follow the Open Source approach: Evolution vs. Revolution. Every time a new Framework comes out it's a complete Revolution. This is EXTREMELY frustrating to try and keep up with.
pulesen replied ago:
It is a thin line to walk on.
Coming from the Java platform, I have sometimes thought that I would like Sun/the JCP process to be a little more aggressive on developing the language. Stuff like generics (which only came with a type erasure implementation) and the upcoming stuff like properties and closures in Java7, have been a loooong way. Sun has really thought about backwards compatibility in such a degree, that the language at some time seemed to stall its development.
Don't get me wrong. I like emphazis on backwards compatibility. But I also like my platform to develop.
Note: In the above, I am only talking about the language itself. It seems the article is talking about lilbraries and frameworks too, in .Net.
Topnotch replied ago:
The key will be avoiding 'accidential complexity'.
ryan baldwin replied ago:
this is an excellent post and something I agree with whole-heartedly. I first began developing with the .NET back when it was in late beta. I've followed it through 1.1, 2.0, 3.0, 3.5, and now all the "splinter" frameworks (such as ASP.NET MVC, etc.) I'm pretty seasoned, and I like to read a lot about what's coming down the pipes, and even I'm terribly confused.
I think MS really dropped the ball with the 3.0 and 3.5 release (but still having them run over top of the 2.0 runtime)... it's just sooooooo confusing as to what version has what, where, when, how, why.... I welcome the day MS wraps it all up under a single distribution again, like they did under the earlier versions.
Like another poster stated, I'm glad to see they've identified the problem and I look forward to them taking the necessary steps to fix it up.
Voters For This Link (13)
Voters Against This Link (1)