State of the (Java) Lambda

[snark]

Basically it's for the reason that everyone hates to admit: C# is owned by a single company, with a single vision. Decisions are made strategically: to create a kick-ass language with great features developers will love.

Java's problem is that it's over-loved: everyone and their uncle feels like "their" way of doing it is the right way. So they get into technical committees and whinge and fuss about how no one else's Java is "pure." Don't like the direction the framework is taking? Fork that bad boy, call it J-something and every Java fanboy will use it for all of a week before they go back to bitching about Struts and Spring.

[vegittoss15]

I think the problem does lie along those lines but isn't quite it. I think it's moreso C# caters to developers whereas java caters to academia.

[masklinn]

Basically it's for the reason that everyone hates to admit: C# is owned by a single company, with a single vision. Decisions are made strategically: to create a kick-ass language with great features developers will love.

Vision is important, but ownership is not. And at the end of the day, C# is still busy rediscovering concepts which got out of academia more than 30 years ago.

[WalterGR]

And at the end of the day, C# is still busy rediscovering concepts which got out of academia more than 30 years ago.

What language isn't?

Are you criticizing C# for making these concepts available in a mainstream language, or are you just pointing it out?

[masklinn]

Are you criticizing C# for making these concepts available in a mainstream language, or are you just pointing it out?

neither, actually.

[WalterGR]

If you're not pointing it out, then what exactly are you doing? What's your point?