Linked by Thom Holwerda on Fri 11th Aug 2006 19:10 UTC, submitted by Dolphin
.NET (dotGNU too) "Four short years ago, Microsoft unveiled its new framework/engine for programming and running applications in a virtual environment, and the world was stunned. Microsoft had introduced a run-time environment that was for the first time a true 'write once, run everywhere' implementation, but that was far from being the end. With .NET 3.0 on the loom, NeoSmart Technologies takes a look at how far .NET has come and just how long it can keep going."
Thread beginning with comment 151584
To view parent comment, click here.
To read all comments associated with this story, please click here.
butters
Member since:
2005-07-08

"and the world was stunned"

and the world was confused, is more like it. At least, that's how I interpreted it, and much of the mainstream IT media outlets agreed. For a while there, no one was quite sure if .NET was a subscription-based business model (Hailstorm), a "Trusted Computing" platform (Palladium), or a sinister attempt to wean developers off of VB.

People often confuse dynamic and interpreted languages. .NET didn't offer a dynamic language until IronPython came along (unless ASP.NET is dynamic, I don't know anything about that). The "write once, run everywhere" dream world is a function of interpreted languages.

I have this equally pie-in-the-sky theory that, with a good JIT compiler, Python/PyGTK/PyQt/wxPython can become a true write-once-run-anywhere development framework. I'd really like to see this happen, because Python really opens up application programming to a less-technical audience, and it makes rapid development a breeze.

I must say, C# turned out better than I thought it would. It's a little verbose and CamelCased for my taste, but you can't please everyone when it comes to syntax.

Reply Parent Score: 4