4 ms·
....quietly reminding the "good, Java sucks anyway" crowd that a vast amount of actually-quite-important commercial software has the JRE as a dep. Like, ok at
by undoware 5y ago
....quietly reminding the "good, Java sucks anyway" crowd that a vast amount of actually-quite-important commercial software has the JRE as a dep.
Like, ok at my end, I kind of shelled out for a license for JetBrains DataGrip, and I'll be really pissed when it stops working on my laptop.
Oh, right, and what if I need to use Gephi? I mean, it pisses me off regularly, but for some stuff it's, like, the only sane way to proceed. Is that just another oops?
Suddenly my Linux desktop is looking a lot less appetizing.
I've been complaining about this problem for two decades: FOSS has a boring-work problem: most maintenance jobs are not exciting, and yield minimal recognition while taking up enormous amounts of time. It's simply irrational to do them.
Commercial software manages this by paying people to do boring work, compensating people with dollars for their otherwise-irrational decision (making it rational.) The pot can be sweetened as need be to keep 'bums in seats'.
But because we compensate one another in attention and reputation (in a manner that is surprisingly reminiscent of the Artworld), we can't just collectively decide to find e.g. maintaining a critical part of the past twenty years of computing patrimony is as hot as greenfielding "X, but in Rust." (and I say this as a burgeoning Rust dev -- it's a beautiful language and ecosystem, no offense meant.)
I mean, we can work on a cultural shift, but we'd best get started as it will take years.
- bzzzt 5y agoThere's nothing preventing you from running Java based applications on Linux. Probably there's already a JRE bundled with the commercial applications you're using. The problem here is some people thought it would be a great idea to use their distribution package manager to also manage Java libraries. Since those are normally bundled with applications you have to manage a lot of incompatible versions and dependencies requiring you to package the entire ecosystem which is a herculean task. That's not a question of boring work but of not being able to scale because you want the whole ecosystem on your terms while not providing value to end users. (and quite a lot of negative value since all packages including the base JDK have been out of date on average the last 15 years)
- Delk 5y agoFWIW, the article now has an update clarifying that it's not the OpenJDK (or JRE) packages that are being orphaned, nor suffering from poor maintenance, but "software written in Java". I suppose that would mean libraries or applications. The JRE and JDK should continue working fine, as should any third-party software that just requires one of those.