2 ms·
Well, it's even worse than that, they caused a breaking change in Java and 2 parallel type systems, if you can call them that, with primitives. They did the sa
by oblio 5y ago
Well, it's even worse than that, they caused a breaking change in Java and 2 parallel type systems, if you can call them that, with primitives.
They did the same for C#, where 2.0 was a breaking change from 1.1.
I still think Go should have bitten the bullet earlier. Though I'm still glad they're doing it now. Just that now there's a ton more code and they're going to divide the ecosystem until adoption is widespread, from the stdlib to every minor corner of the ecosystem that needs it.
- EdwardDiego 5y ago> Well, it's even worse than that, they caused a breaking change in Java What breaking change? They implemented type erasure specifically not to break existing code.
- oblio 5y agoBad wording, sorry. It was breaking for C#, for Java I wasn't breaking, just ecosystem diving. For example, Hibernate still doesn't use generics fully, from what I remember (they had their half baked system from before). Adding them later is such a big change that touches so much code you can date it into pre generics/post generics:-)