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 147235
To view parent comment, click here.
To read all comments associated with this story, please click here.
Lambda
Member since:
2006-07-28

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.


Then you get into more weird special cases like String. In .NET operator overloading is not CLS compliant, so the CLS compliant libraries have to have an alternative non-operator overloaded method. So you have the choice to use or not use operator overloading. I'd rather have a team decision on whether to use them, then let Sun be the decision maker.

Reply Parent Score: 1