Linked by Eugenia Loli on Fri 28th Jul 2006 18:28 UTC
.NET (dotGNU too) Microsoft is leaving Java in the dust, but the company still has room to grow in the developer arena, a key executive said. Speaking at the Microsoft FAM (Financial Analyst Meeting) on July 27 in Redmond, Wash., Bob Muglia, Microsoft's senior vice president of Server and Tools business, said Microsoft's .Net platform has outpaced Java, particularly the Java Enterprise Edition, over the past five years to become the development platform of choice for enterprise development.
Thread beginning with comment 147152
To view parent comment, click here.
To read all comments associated with this story, please click here.
Lambda
Member since:
2006-07-28

I believe operator overloading was specifically avoided in Java because it's simply bad style, in most situations, and even when it's not it's often abused.

But then you start using BigInteger or BigDecimal and realize that non-operator overloading is bad style. Bad style and abuse is indicative of bad developers, not operator overloading.

Reply Parent Score: 4

ma_d Member since:
2005-06-29

It's a different problem. Bad names are one problem, doing operations that call unknown functions are a whole other problem. Operator overloading hides in single characters in your code, and you have to dig around for it.

Reply Parent Score: 1

Lambda Member since:
2006-07-28

Operator overloading hides in single characters in your code, and you have to dig around for it.

You won't have to dig around anymore than any other function with a smart editor. But "digging around" is a symptom of Java-style OO and inheritance in general. Overloaded operators are just like any other function (at least in most languages).

Here http://relo.csail.mit.edu/documentation/relo-vlhcc06.pdf is an interesting paper on the rational for a eclipse plugin called Relo that aids in that "digging around" of large class trees.

Reply Parent Score: 1

dextar78 Member since:
2006-04-02

I believe operator overloading was specifically avoided in Java because it's simply bad style, in most situations, and even when it's not it's often abused.

Infact, Java already has some form of operator overloading. For example, when you write:

String line = "X = " + x + ", Y = " + y;

You begin to realize how useful operator overloading is. Why can't this be extend to other classes (like BigDecimal & BigInteger as mentioned above), or even our own?

Reply Parent Score: 1