4 ms·
Well, ain't I smart. I said, loudly, at the first JavaOne conference that Java was exciting, but Java applets were a bad idea. "Write Once Run Anywhere" would b
by jfengel 6y ago
Well, ain't I smart. I said, loudly, at the first JavaOne conference that Java was exciting, but Java applets were a bad idea. "Write Once Run Anywhere" would be killed by version mismatches even before it got killed by everything else.
And 25 years later, I was right! Go me.
Personally, I think the real problem was that for some reason Java never had access to the DOM. Java Applets always felt half-assed because they weren't anybody's home, while Javascript made for UIs that users felt at home with because they were native to the browser. That didn't fix the bajillion versioning problems and need for shims and other crud, but right off the bat Java UIs never felt right -- either AWT or Swing.
(And neither did GWT or SWT.)
I'll always wonder what would have happened the JVM were really properly integrated into browsers. I suppose we could target WebAssembly now but it doesn't really matter: TypeScript is a not-terrible language. Not as good as Java and not as good as languages like Kotlin that learned from Java's mistakes, but good enough.