3 ms·
A 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
by eropple 12y ago
A 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.
- oldmanjay 12y agoit's easy to be aggressive when you risk nothing. that's about the only lesson I've taken from your posts.
- skybrian 12y agoYes, you're probably right that they don't care about your business. Oracle's actual customers are large businesses running hundreds of millions of lines of code and they probably don't understand all of it. They probably care a lot about preserving their existing investment. If they decide to put off upgrading to the latest VM, Oracle can't sell them stuff. The point here is to have some empathy. There are other people in the world with different priorities. You can't say whether a technical decision is good or bad without understanding what they're trying to do.
- coldtea 12y ago>Yes, you're probably right that they don't care about your business. Oracle's actual customers are large businesses running hundreds of millions of lines of code and they probably don't understand all of it. That was true for SGI, HP, DEC, SUN etc at some point too. See how the ended when they didn't adapt? SUN could still be alive and be pioneering all this cloud and web programming in 2014... They could have created something like Heroku (or lower level like AWS), they could have added some flexible Rubu/Python Django/Rails like option for the JVM (instead relying on third party ho-hum small attempts). They could have pioneered the big data space. Instead the insisted on Java for everything, and kept it as stale as they could. This is were it got them...
- skybrian 12y agoThey did try. Sun had all sorts of innovative projects that didn't work out (such as JavaFX), but they've been forgotten. Java on the server is what remains. It may not be flashy, but it's a survivor (still around even after Sun is dead) and it's likely to last as long as Fortran and COBOL. It's only in the early adopter community that survival doesn't seem to count for anything.
- eropple 12y agoI'm stating what I want in my tools. I've been very clear that, while I am entirely convinced that they are wrong and will suffer for it, they can do whatever the hell they want and I'll respond in kind. Where is the lack of empathy here? And, as coldtea notes, lashing themselves to boat anchors hasn't done Java, or Java's owners, much good throughout its history.
- skybrian 12y agoThere's nothing wrong with saying what you want in your tools. But it's rather weird (though a common sort of move on the Internet) to follow that up by saying that the Java maintainers are making the wrong decision and therefore they are courting disaster. Why draw that conclusion? I'm assuming you're not so much of an egotist to think your desires are that important? A more reasonable conclusion would be that what I want, or what you want, and what's good for Java have little to do with each other. You should use another language that fits better (since you're fortunate to be free to switch), and Java will probably be fine.