Sorry Java, Write Once Run Anywhere (WORA) Is Now JavaScript
medium.com
medium.com
With Java the code, dependency management, and build tools just work. It's very pleasant to maintain.
Maintaining a JS project over more than a few years is a nightmare. Forced rewrites as libraries, build tools, linters, frameworks, and the language itself are constantly being reinvented. It's a huge pointless drain on resources.
And JS is awful cross-platform. You have to check and polyfill every feature if you want to work outside latest Chrome and Firefox. And transpile the code down to ES5.
With Java it runs exactly the same on every platform. We develop on Macs and run on Linux and it doesn't even matter.
In any case, sorry JavaScript, Java is still WORA, even on iOS and on the browser, it is only a matter to actually bother to learn where to get the tools from.
Safari browser.
Clear history.
Develop / Empty caches.
Preferences / Security / uncheck Enable JavaScript
I get the full article.
I don't know if all that is truly necessary. I instead generally browse in Firefox with NoScript and with preference "Clear history when Firefox closes".
That also results in the full article.
Most of these sites rely on either JavaScript and/or cookies. Both of which are trivially bypassed with a few seconds of effort. That also includes sites like NY Times and Bloomberg, which are also linked on HN frequently.
Hard firewalls like WSJ and FT are more difficult to get around. But almost invariably someone will post a link to archive.(some-random-tld).
Transpilers have extended Java's reach quite a bit, for me.
The JVM doesn’t exist on iOS.
People have to start learning not to mix languages with implementations.
Looks WORA to me.
It was obviously the main selling point for Java for a long time but it never really had a good story for the front end although I know Google for example had a number of frameworks that did exactly this (GWT / Closure).
Fundamentally the only thing that ran inside the browser was JavaScript which was a shame because that meant that for everyone who wanted to use a single language was forced to use it everywhere else which gave rise to things like Node, React Native and Electron etc.
The best solution we had between those two options was to make an attempt to transpile other languages like Dart and TypeScript into JavaScript in order to overcome its shortcomings.
While the reality of this is still a long way off I think the idea of WASM / WASI as a new platform that “all” languages could theoretically target is one of the more exciting prospects coming down the pipeline in terms of the WORA dream. I think it’s fair to say that it also has the potential to move the needle in a significant way for the “browser as an app platform” story.
The question then becomes where does that leave us with JavaScript when you take away it’s main advantage.
On the backend as well there are a lot of interesting things happening. Containers have gone from requiring a lot of complexity (kubernetes) to dead simple (knative / Google cloud run) where you just ship a container and everything works out of the box. Combined with things like gRPC on the backend and also coming to the browser I feel like the future of application development is looking genuinely exciting.
Write once, debug everywhere, consume all the a RAM, have poor integration in all desktop, full of glitches in Linux.
It's also difficult to run electron apps under wine so ultimately it results in less Linux apps.
Wikipedia attributes the phrase to SUN Microsystems and Java but, with weasel words admits that the same idea was baked into UCSD Pascal.
https://www.leaningtech.com/pages/cheerpj.html
Have fun running the Swing and JavaFX demos.
As mentioned on my other comment, it is a matter to care to learn about the tools.