Re:C# isn't a language...
on
Head First C#
·
· Score: 1
The main problem in C++ and C# is that just looking at a statement you can never be sure what it does without poking around a lot of places (in Java a statement always says exactly what it does). A simple statement like "x.y = a[b]" can involve at least 6 different method calls.
That stinking operator overloading! I hear that in C++ and C# something like:
s1 == s2
could even compare VALUES of two strings s1 s2! Instead of checking whether s1 and s2 two references point to the same object in memory, like every sane language should do.
And all those other things. I mean, in C++ you also had to deal with templates, those complicated buggers. I mean, dude, you'd even have to write something like vector<int> - instead of plain old simple Object containers that you'd only have to cast into the target type - the way that statically typed language are damn well supposed to be. Oh wait, we decided that the <Integer> thing was better in 1.5? Kahm...
And I hear that there are some other things where you could even hook into language constructs, such as the for loop, instead of using the simple iterator()/hasNext()/next() idiom. Oh crap, we did that too in 1.5 with Iterable???
It's not that I hate Java... too much. Yes, it is a good, robust platform with a myriad of tools, well suited for big project and enterprises. Yes, no-one can dispute that C++ had a number of completely unnecessary features (private inheritance, anyone?) but the amount of straitjacketing that Java imposes on you is completely unnecessary - as they admitted themselves on those two examples above. Only 10 years later.
Don't ditch C# just because it's from Redmond. They got a number of language things right IMHO (not saying that they haven't got a number of them wrong as well). If anything, having a competitor is good for Java and for all of us at the end.
Of course, I'd take Python or Ruby over both them C++ clones any given day.
Slashdot Mirror
Posted by Dirk Diggler MPD
;)
you're saying it's not because of the DNS vulnerability?
A black man's weenie?
and sell it to this guy.
There are only two things I can't stand in this world. People who are intolerant of other people's cultures... and the Dutch.
True, SVG should be a standard available on all browsers, but only FF supports it. Such a pity.
Not true.
The main problem in C++ and C# is that just looking at a statement you can never be sure what it does without poking around a lot of places (in Java a statement always says exactly what it does). A simple statement like "x.y = a[b]" can involve at least 6 different method calls.
That stinking operator overloading! I hear that in C++ and C# something like:
s1 == s2
could even compare VALUES of two strings s1 s2! Instead of checking whether s1 and s2 two references point to the same object in memory, like every sane language should do.
And all those other things. I mean, in C++ you also had to deal with templates, those complicated buggers. I mean, dude, you'd even have to write something like vector<int> - instead of plain old simple Object containers that you'd only have to cast into the target type - the way that statically typed language are damn well supposed to be. Oh wait, we decided that the <Integer> thing was better in 1.5? Kahm...
And I hear that there are some other things where you could even hook into language constructs, such as the for loop, instead of using the simple iterator()/hasNext()/next() idiom. Oh crap, we did that too in 1.5 with Iterable???
It's not that I hate Java... too much. Yes, it is a good, robust platform with a myriad of tools, well suited for big project and enterprises. Yes, no-one can dispute that C++ had a number of completely unnecessary features (private inheritance, anyone?) but the amount of straitjacketing that Java imposes on you is completely unnecessary - as they admitted themselves on those two examples above. Only 10 years later.
Don't ditch C# just because it's from Redmond. They got a number of language things right IMHO (not saying that they haven't got a number of them wrong as well). If anything, having a competitor is good for Java and for all of us at the end.
Of course, I'd take Python or Ruby over both them C++ clones any given day.