"C# As a language, C# isn't bad. Unfortunately, it's tied closely to Microsoft's bloated ".NET" environment. The language itself is fast, hard-compilable, and safe. It needs garbage collection, but so be it. "
Every safe language has to have garbage collector or else it isn't safe. Because if C# let you use C 'free(void* p)' or C++ 'delete' that would mean you could free (and later allocate elsewhere) memory that is still in use - which isn't safe. Therefore resource deallocation must not be handled by programmer, but rather system - garbage collector.
Ahm, this is obviously the same kid that wrote the first part, I'd say he probably never got beyond what they've taught him in college (not much I suppose) - he claims developers are still writing directly to win32 api.
Dunno, but he must be living really, really deep in the cave as developers have been using higher level, object oriented libraries for like a decade and more. I have no idea why this rubbish even gets on the front page (ok I know, it bashes Windows and we like to do that, right comrades?)
Now win32 is exactly the same rubbish as posix, they are both basically just C style functions.. there is no object-oriented design because it was designed long ago, when processor cycles mattered more than today and if they really wanted to waste those cycles they could easily wrote whole damn OS in python. Efficiency, it matters. Now stupid developer (or library writer) will use win32, but a smart developer will rather choose libraries like wxWidgets, MFC or even Java or.NET.
And it's just plain lunacy to say.NET is insufficient. It is the best strongly typed framework, its C# is java 2.0, you can even fuse machine code(x86) into the same binary with C++\CLI and get flexibility and raw power of C++ to do just anything.
He also seems to be very quiet about some of the new stuff in.net languages like linq - or APIs like WPF, which is IMO just the most powerful gui creation library (and by that I mean this - this and this), but unfortuantely only available on windows.
So yeah, I'd say the author has completely no idea what he's talking about..
Slashdot Mirror
"C# As a language, C# isn't bad. Unfortunately, it's tied closely to Microsoft's bloated ".NET" environment. The language itself is fast, hard-compilable, and safe. It needs garbage collection, but so be it. "
Every safe language has to have garbage collector or else it isn't safe. Because if C# let you use C 'free(void* p)' or C++ 'delete' that would mean you could free (and later allocate elsewhere) memory that is still in use - which isn't safe. Therefore resource deallocation must not be handled by programmer, but rather system - garbage collector.
Ahm, this is obviously the same kid that wrote the first part, I'd say he probably never got beyond what they've taught him in college (not much I suppose) - he claims developers are still writing directly to win32 api.
.NET.
.NET is insufficient. It is the best strongly typed framework, its C# is java 2.0, you can even fuse machine code(x86) into the same binary with C++\CLI and get flexibility and raw power of C++ to do just anything.
.net languages like linq - or APIs like WPF, which is IMO just the most powerful gui creation library (and by that I mean this - this and this), but unfortuantely only available on windows.
Dunno, but he must be living really, really deep in the cave as developers have been using higher level, object oriented libraries for like a decade and more. I have no idea why this rubbish even gets on the front page (ok I know, it bashes Windows and we like to do that, right comrades?)
Now win32 is exactly the same rubbish as posix, they are both basically just C style functions.. there is no object-oriented design because it was designed long ago, when processor cycles mattered more than today and if they really wanted to waste those cycles they could easily wrote whole damn OS in python. Efficiency, it matters. Now stupid developer (or library writer) will use win32, but a smart developer will rather choose libraries like wxWidgets, MFC or even Java or
And it's just plain lunacy to say
He also seems to be very quiet about some of the new stuff in
So yeah, I'd say the author has completely no idea what he's talking about..