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 147158
To view parent comment, click here.
To read all comments associated with this story, please click here.
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

evangs Member since:
2005-07-07

The problem with operator overloading is that it doesn't immediately make it clear to the programmer what's happening when you see a line of code. I used to be in the C++ camp, firmly believing that the lack of operator overloading in Java was a bad thing. After having to spend months looking at someone else's C++ code, I'm singing a different tune.

On the other hand, classes like BigDecimal and BigInteger should be treated like String. String has the overloaded + operator, and since BigDecimal and BigInteger are part of the official Java platform, I feel that Sun should have implemented operator overloading for these classes. Operator overloading usually only makes sense when you're writing classes that deal with numeric values of some sort, like a vector or a matrix. Seeing as Java provides all sorts of stuff like XML processing, *two* GUI toolkits, implementing classes like matrices and vectors shouldn't be too much to ask for.

Reply Parent Score: 1