- LittleBigPlanet Kratos / 007 Quantum of Solace Code Contest
- Is the GPhone a Trolltech Greenphone or Neo1973? [updated]
- EVE Cheaters Lead Gilded Lives
- Mobile: Opera Mini
- PSPWorld's Top 10 Shows Platform Weakness
- EA Lets You Try, Try Again Installing Spore
- AdhocParty Expands To Over 100 Titles
- Home Muzzled, GTA4 Still Great
- zOMG! It's Totally A Flash MMO!
- Save Room At The Table For Killzone 2
.NET 3.0: Compatibility is Microsoft's Problem?
Sun, 2006-08-06 06:39 — PMunn
Look, Vista is unreleased, .NET 3.0 for Vista is unreleased, and .NET 3.0 for XP is unreleased, and this guy thinks he can bank on the fact that Microsoft will assure compatibility across both platforms?
Not knowing much of anything about what .NET 3.0 will offer the development world, I found this blog entry interesting for a couple of reasons.
http://neosmart.net/blog/archives/233
Quote:
The .NET Framework is not actually an API as much as it is a communication layer that transforms specialized commands and arbitrary functions to low-level understandable sequences that the operating system then carries out. What all this means is, after .NET 3.0 RTMs, compatibility becomes Microsofts problem. If you have a program that runs on XP with .NET 3.0 RTM installed, you shouldnt have to lose sleep wondering whether itll still work when Vista goes Gold it will and thats that.
Look, Vista is unreleased, .NET 3.0 for Vista is unreleased, and .NET 3.0 for XP is unreleased, and this guy thinks he can bank on the fact that Microsoft will assure compatibility across both platforms?
He really should talk to the Java people on how patently false any such statement is likely to be. Two platforms = two sets of bugs. Microsoft = not known for shipping non-beta 1.0 code. End of story.
Post new comment