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 147147
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Sun's problem with the ftuture
by ma_d on Fri 28th Jul 2006 20:04 UTC in reply to "Sun's problem with the ftuture"
ma_d
Member since:
2005-06-29

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.

I'm not sure why properties haven't been adopted by Java or most anywhere else that I've noticed. I always liked the idea. I suppose it would be confusing in Java now as everyone uses setters and getters, you'd be asking "setters/getters or properties" for each class and that'd be irritating.

PS- Scala has perked my interest.

Reply Parent Score: 1

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

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

Ronald Vos Member since:
2005-07-06

Scala has sparked my interest as well. It's like OCaml, but even better and more modern.
Exciting like Boo, but with features that seem more useful.

Reply Parent Score: 1