upvote

points

by Someone9 hours ago |
comments
upvoteby toyg8 hours ago|
[-]
This. C# was basically always meant to be "Java but done right". It came several years later, after Microsoft was legally barred from "EEE"-ing Java and required a direct competitor.
reply
upvoteby newsoftheday5 hours ago|
parent|
next
[-]
> It came several years later, after Microsoft was legally barred

That is an eloquent way of re-writing the history of Microsoft stealing Java and not being allowed to get away with it.

reply
upvoteby toyg4 hours ago|
parent|
[-]
They didn't "steal" anything, iirc; they started as a legitimate licensee and then tried their usual embrace/extend/extinguish as "J++" (the EEE I mentioned). Sun sued for breach of license and won, barring Microsoft from extending Java outside of the (Sun-controlled) process. So they dropped it and built their own version, with blackjack and hookers.
reply
upvoteby dingi3 hours ago|
parent|
[-]
> So they dropped it and built their own version, with blackjack and hookers.

This cracked me up

reply
upvoteby cm21877 hours ago|
parent|
prev|
next
[-]
But what I don’t get reading the original article is that they present how to insert struct in an object oriented language as an intractable problem, whereas a good implementation with .net (as far as I can tell) has been out there for nearly 30 years. And C# was shameless about stealing from other languages.
reply
upvoteby Someone7 hours ago|
parent|
next
[-]
> how to insert struct in an object oriented language as an intractable problem, whereas a good implementation with .net (as far as I can tell) has been out there for nearly 30 years. And C# was shameless about stealing from other languages.

I think (but may be wrong) their concerns are about the insert part. C# always had structs, Java wants to add them in a backward-compatible way. They want, for example, existing generic container classes pulled in from a .jar (i.e. already compiled) to support Java value types.

reply
upvoteby pjmlp7 hours ago|
parent|
prev|
next
[-]
The problem is how to do it without breaking ABI, 30 years of Maven Central is very relevant, Java isn't doing a Python over value types.
reply
upvoteby cm21876 hours ago|
parent|
[-]
But if you define a new type, how is that breaking backward compatibility?
reply
upvoteby pjmlp6 hours ago|
parent|
[-]
Because that is missing the point.

All the types that are value types in semantics, e.g. Optional, should be proper value types on Valhalla.

Additionally, they should be compatible with existing code that expects them as parameters, fields,.... without being recompiled from source.

If it is a complete new type without backwards compatibility, no one is going to adopt it, other than a few niche cases.

reply
upvoteby Zardoz846 hours ago|
parent|
prev|
[-]
Dlang this this before. You have classes and struts, with different semantics.
reply
upvoteby pjmlp7 hours ago|
parent|
prev|
[-]
Ironically, they still do need Java for Azure, https://devblogs.microsoft.com/java
reply