Linked by R_T_F_M on Thu 13th Sep 2012 21:19 UTC
FreeBSD "For the past several years we've been working towards migrating from GCC to Clang/LLVM as our default compiler. We intend to ship FreeBSD 10.0 with Clang as the default compiler on i386 and amd64 platforms. To this end, we will make WITH_CLANG_IS_CC the default on i386 and amd64 platforms on November 4th."
Permalink for comment 535289
To read all comments associated with this story, please click here.
RE[16]: C++
by boldingd on Sun 16th Sep 2012 02:48 UTC in reply to "RE[15]: C++"
boldingd
Member since:
2009-02-19

Funny, because here in Germany I get called every single week for new Java projects. My employer has lots of Java projects proposals without enough developers to take care of them all.

That does not look like loss of mind-share to me.


I admit that I have no solid empiracal measure of language usage or user-base growth, but I have the strong impression that Java as a general-purpose desktop application language is dieing. It isn't being shipped on new Windows machines anymore, new software projects aren't using Java, the language is fading away. It certainly still has its users -- I've written an internal-use web service in JSP, and it's Android's native language, after all -- but I think it's days as a general-use language are pretty much over.

Now I agree with you that generics in Java suck, and I also don't like the way the language is going with the annotation overload that it is getting (@override, @value, ...).

For me, Java is just another tool. The language I use, always depends on the project requirements, and is usually already decided by the customer.


I never said that generics in Java sucked! I'm glad they finally got them, long overdue as they where. Given how much more type-safe generics make abstract container classes, I was saying that it was a crying shame that it took Sun so long to break down and add generics into the language!

To me, that's the story of the growth of Java. They looked at C++ and said "there's gotta be a simpler way to build a language." (And for my money, they're right on that.) So they stripped out a lot of the most confusing features and worst design decisions, and Java was what they where left with. But they took out to much; things like generics, while ugly from a type-flexible pure OOP perspective, end up being net benefits for the language. And they where too slow to add those features back into Java. So you're left with an under-expressive language that's missing features that older languages have had since before Java existed.

I mean, Java finally gets what amount to a Python with-block in Java 7, in 2012? Why the hell did it take that long? And why is the RAII block that we finally do get merged with try-catch blocks? What would've been so bad about introducing a with block?

Reply Parent Score: 2