Slashdot Mirror
Microsoft Developers Respond To .NET Criticism
bonch writes "Richard Grimes of Dr. Dobbs Journal wrote an article entitled Mr. Grimes' Farewell, in which he discusses what he feels are inherent flaws in .NET, and how he is abandoning his .NET column. Grimes argues that .NET is merely thin wrappers to Win32 calls (Avalon uses message functions that date back to 16-bit Windows), that Microsoft has abandoned confidence in both .NET and sales of Longhorn, and that the framework itself is too large and poorly implemented, most of it ported from past APIs like WFC and VB. Dan Fernandez, Microsoft's Visual C# Project Manager, has responded in his blog. Richard Grimes appears in the comments to defend his criticism, referencing first-hand disassembly of .NET APIs using ildasm. Scott Swigart has also responded to the criticism of Visual Basic .NET. Apparently, Mr. Grimes struck some nerves."
Microsoft is geared around job creation (bless them) - if they made APIs that made sense then you would need less programmers and less hours to complete a task, anyone with 101 business can see that this means less jobs and somehow in a round about economic sense this means less money for microsoft. You see, in business, when a cost is significantly cut (eg by firing workers and replacing them with looms) a excess amount of money is 'freed', companies don't like excess money because it upsets accountants so someone needs to take it, that someone is the loom technician who is invested in to keep making more looms, everyone is happy.
This comment does not represent the views or opinions of the user.
Except for having to use Perl. Ass language of the highest order.
In what ways does C Sharp look "much nicer" than Java, given their practically identical syntax?
C# has some crucial differences in its functionality and semantics.
Also, would you care to estimate the ratio of FOSS and Linux code written in Java to that written in C Sharp?
Well, what matters to me is not how much FOSS there is that runs on proprietary Java implementations, but how much FOSS there is that runs on FOSS Java implementations, and the answer is: not much.
The best bet for an open source Java environment would be gcj with SWT, but having looked at that, I think it's far less appealing of a platform than Mono/Gnome.
Microsoft's track record with browser-based applications is one security disaster after another. Their existing browser-centric security model is fragile that I can't see a way to fix it without changing the API and breaking every application that uses it.
.NET? (hint: its wtf we're talking about). It is by no means browser-centric and in fact, Visual Studio contain schemas for different browser platforms. Don't create idiotic and uninformed FUD.
Uhm, ever heard of