4 ms·
The response by Brian Goetz[1] is kind of unpleasant and combative. Moreover, the ideas in it kind of encapsulate why I'm growing more and more uncomfortable wi
by eropple 12y ago
The response by Brian Goetz[1] is kind of unpleasant and combative. Moreover, the ideas in it kind of encapsulate why I'm growing more and more uncomfortable with relying on the JVM to keep up with my needs in the future.
> The cost of the C# approach is that existing
classes could not be gradually migrated to be generic; existing collections had to be effectively deprecated and replaced, or a "flag day" had to be declared where all the code (library and client) changes simultaneously. These are not options for us.
This is why, despite doing it in my day job, I'm not high on the JVM's future as it stands right now. Compatibility uber alles is not a virtue, even Microsoft gets that these days. Saying "on 1 Jan 2017 we're pushing Java 10, and you will need to recompile your dependencies to upgrade" is not a bad thing. No, many people won't upgrade immediately. That's true. But they already don't! It takes years for consumers to catch up with the newest version of Java (for reasons that do not reflect well on those consumers). Why should I, as a consumer, care about them? Why should I, as a consumer, continue to use your product when you would care about laggards more than me? I mean, Oracle's welcome to, it's their business, but why would I respond positively to that?
But he says that a flag day means they "hate their users." No, it would mean they are going to firewall off the damage laggards can do to their environment and ecosystem. And for the sake of a healthy platform for the next decade I would think they should do exactly that, because those laggards don't make the ecosystem and the environment better.
And then, at the very end:
> And, feel free to prove us wrong! Try implementing the changes you are envisioning in the JVM, and show how they can get us to the goal!
Why should I, guy-who-works-for-Oracle? I'm not drawing a paycheck from Oracle, who owns Java so utterly and wants to attack and damage related tools and platforms (hi, Android), and guess what? I really don't need Oracle to fix this because in 2015 I am going to have options. Microsoft is releasing an open-source CLR for OS X and Linux and it's effectively substitutable for just about anything I care to use (and, if I had to be honest, a combination of C# and F# are probably better than even Scala for what I do). This is Oracle's problem and Oracle's ground to lose, not mine.
Two-thirds of my Github are C# and Ruby at this point, anyway, and I don't even use C# for work.
[1] - http://mail.openjdk.java.net/pipermail/valhalla-dev/2014-December/000475.html http://mail.openjdk.java.net/pipermail/valhalla-dev/2014-Dec...
- skybrian 12y agoIt sounds like you do hate Java's users. You dismiss the difficulty of upgrading existing apps, which is an enormous amount of work, without even making a rough estimate of how hard it would be. They are just "laggards" to you. At least consider that others may have different values than you and actually care about these people. Sacrificing backward compatibility means adding pain for existing users in the hope that the world will be better for new users. Splitting the community on purpose has a cost; just look at python 3 for how painful this is. Whether this makes sense depends very much on the size of your existing user base and on the potential for growth. The users you gain by making a language somewhat more elegant may not be worth the loss from the disruption.
- eropple 12y agoA flag day on a bytecode format is "hating users"? It's a Python 3 split? Come on now. Heck, I can't come up with anything (and I've been thinking about this a lot for a few weeks, as I spend more personal time in C# and getting stuff done quickly that's kind of a pain in Java) that'd prevent automatic translation of pre-flag bytecode to an equivalent matching the old code's intent. If a jar has a pre-flag bytecode format, then rewrite to treat those parameters at runtime as T => Object and transparently box value types that are supplied for T. The pre-flag jar still contains the necessary information for the compiler to throw a rod if generic constraints are violated. (You could even experiment with more restrictive runtime constraints, but I haven't thought through the implications thereof.) But you know? If it takes laggards three years instead of the usual two to jump from Java 9 to Java 10, I don't care. I shouldn't care, because I'm not them. Oracle might. They can do that. But Oracle doesn't want my business if they do to my detriment, and the more time I spend outside the JVM the more annoyed I am by their self-imposed limitations. Microsoft seems like they wouldn't mind my business, though, which is faintly astonishing. I'm happy giving it to them if they're going to provide a better product. (I'm reserving judgment until we see their Linux and OS X ports of their CLR, but I'm high on it.) And if you're seriously going to get riled up about "laggards", I hope you never take an economics class, because they think words mean things and I do too.
- 12y ago