A lot of people have trouble understanding what .NET really is and what its goals are. Mostly because Microsoft has done a good job of confusing everybody using terms that are not self-explanatory or with terms that mean more that one thing. This editorial will present my thoughts on .NET, what it really is, what its motivations and goals are, and why it is the next "big thing." Should we embrace it or fear it? Both, I daresay.
Permalink for comment
To read all comments associated with this story, please click here.
> Microsoft does the following better than any other OS
> platform:
> - Localization, into 34 locales at last count
Oh *please*, this is a joke, yes? AmigaOS did that better in 1987, without the need to provide different *binaries* for each locale. (For those who don't know / remember, by providing a .catalog file in addition to the binary. It was even possible to add new locales without having the source code of the binaries.)
It might not matter to you, but it gives me stampeding madness when the latest bug in Windows is fixed in the US version, "fixes for other locales coming soon". That's stupid to the extremes.
> Microsoft does the following better than any other OS
> platform:
> - Localization, into 34 locales at last count
Oh *please*, this is a joke, yes? AmigaOS did that better in 1987, without the need to provide different *binaries* for each locale. (For those who don't know / remember, by providing a .catalog file in addition to the binary. It was even possible to add new locales without having the source code of the binaries.)
It might not matter to you, but it gives me stampeding madness when the latest bug in Windows is fixed in the US version, "fixes for other locales coming soon". That's stupid to the extremes.
Check your mileage, it varies from reality.