Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
As I said, the author of that "FAQ" frequently goes on C# newsgroups for the express purpose of stirring up controversy. He acts like he's a 15 year old jerk. Why os it so important to you to complain about C#? Do you consider the languge a threat to Java? Do you feel that your career is in danger because of C#?Originally posted by Apu Petilon:
If you run out of arguments, resort to name calling. And they made you a moderator. How ironic!
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
Originally posted by Thomas Paul:
So we agree that operator overloading is not a wise thing in a language in most cases.
So what? In order for C# to be compatible with C++ it was included in the language. Perhaps it was a mistake but I think the fact that Microsoft was concerned about C++ developers is very commendable.
As far as the next release of C#, it could very well come from ECMA, not Microsoft.
And agian, since you have never posted to JavaRanch except to complain about C#, I consider you a troll. Why not spend your time helping Java developers become better Java developers instead of complaining about C#?
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
You have now demonstrated that you don't know what you are talking about. A C# program can inherit from a managed C++ class. It can invoke methods of a C++ class (managed or otherwise). They can live together very happily in the .Net environment.
As far as indexers and properties, I can see how a VB programmer would be confused by them. But then most VB programmers have very little exposure to OO.
Originally posted by Ravi Veeraghanta:
Also be nice enough to leave a note when you are moving topics from one forum to another.
Originally posted by Apu Petilon:
Thank you for the kind words, Randall. Most programmers spend more time maintaining code written by other people than writing new code. More time will be spent reading and maintaining code than writing it in the first place. Because of this, code maintainability is more important than saving a few keystrokes when writing it initially. A lot of professional programmers ufortunately don't understand this. Hopefully I can convince a few people here.
Originally posted by Thomas Paul:
You said: C# is not compatible with C++.
You have now demonstrated that you don't know what you are talking about. A C# program can inherit from a managed C++ class. It can invoke methods of a C++ class (managed or otherwise). They can live together very happily in the .Net environment.
As far as indexers and properties, I can see how a VB programmer would be confused by them. But then most VB programmers have very little exposure to OO.
And I wasn't telling you what to do with your time. I was making a suggestion that spending your time worrying about C# is a waste of your time. Why don't you let the C# programmers worry about their language and you worry about yours?
I still don't understand the obsession that Java programmers have with C#. Is it really that scary to you? Or is it really that important to you that you "prove" that Java is a better language? When you are finished with C# will you go argue with the Python programmers?
Makes sense. So I won't bother spending anymore time with you.Originally posted by Apu Petilon:
Why don't you let me worry about how I spend my time, and you worry about how you spend yours? How about that?
Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
"Thanks to Indian media who has over the period of time swiped out intellectual taste from mass Indian population." - Chetan Parekh