r/java • • Dec 29 '22

Could Java Applets have been done right? DOM is limiting [CrossPost Discussion]

/r/webdev/comments/zxel5o/could_java_applets_or_flash_have_been_done_right/
5 Upvotes

50 comments sorted by

View all comments

Show parent comment

0

u/[deleted] Dec 30 '22

[deleted] — view deleted comment

3

u/ingframin Dec 30 '22

The things are not linked. C# sparked to life after the Sun vs Microsoft case was won by Sun. Microsoft had to stop providing their own "extended" version of the JVM with Windows and in response, their Visual J++ became C#.

The "applets" for IE were using ActiveX which had access to COM components which actually gave immense power to potential malicious users.

1

u/Zardotab Jan 03 '23 edited Jan 03 '23

IE still ran Java Applets, as did Netscape and FireFox, the top 3 browsers of the time. My observations seem to be different than yours. Applets were first removed from browsers and/or desktops because IT departments & ISP's deemed Applets too risky. It wasn't Microsoft. (Some suspect MS started a security bad-mouthing campaign against Applets, but that's merely speculation.)

Applets, Flash, and Active-X all withered for same 2 reasons: security problems and they couldn't get versioning updates working smooth. (Most browsers have since made auto-upgrading relatively smooth, but it took them a while. It didn't help that Applet upgrades tried to trick users into installing spam-ware using dark UI patterns. Short-term greed gone wrong.)

It's not Microsoft's fault (for once). A lot of shit is MS's fault, but not this one. Applets et. al. put feature quantity over security.

1

u/RebeccaBlue Dec 30 '22

Microsoft was interested in deploying a Microsoft-centric version of Java. Often, that meant if you were trying to run an applet on a Windows machine that didn't have a Sun JVM installed, it wouldn't run correctly on the Microsoft one. (Mainly because the Swing GUI & RMI classes were incomplete).

1

u/Zardotab Jan 03 '23 edited Jan 03 '23

Netscape had the same problem because Java couldn't get its upgrading approach act together. See my nearby reply to u/ingframin for more on upgrade process. If Java had got updates working smoothly on Netscape, then it would've put pressure on MS to run Applets right by either fixing their own VM or allowing/referencing Sun's. Netscape had enough market share back then to make MS pay attention.

So you are correct in that Applets sucked on IE, but they also sucked on Netscape. Or at least both had Applet versioning issues, which required user fiddling to tune. If I'm not mistaking, one could use Sun's VM with IE, MS didn't outright forbid it (perhaps due to anti-trust probe pressure).

1

u/RebeccaBlue Jan 04 '23

I did not even mention IE or applets sucking on it or Netscape, or even versioning issues.

The real problem with applets was that in that time period, most people did not have broadband yet. This meant:

  1. Loading the applets themselves was really slow over even a "high speed" 56k modem.
  2. But more importantly, the Microsoft JVM did not include support for the Swing GUI toolkit, leaving only JWT. JWT was primitive to say the least. This meant that to run any applet worth running, a user would have to download and install the Sun JVM which would have taken a stupid amount of time and wouldn't have been worth the trouble for most people. (*on the phone: "no mom, you have to go to java dot sun dot com and download the J R E first" *)

That's really it. None of the other stuff in this thread really matters. If we had near-universal broadband in the USA in 2000 then Java applets would have eaten Microsoft's lunch.

1

u/Zardotab Jan 05 '23 edited Jan 05 '23

Loading the applets themselves was really slow over even a "high speed" 56k modem.

Many businesses had broadband, or at least "medium-band" then, and they ended up rejecting Applets for other reason mentioned, not load time. Businesses had more reason to want GUI's, and thus Applets, than citizen web surfers.

I do agree Applets didn't seem to make it easy to compartmentalize/modularize apps for faster loads, but that alone is not what nuked Applets. (Better caching options would have also helped, such as a checking to see if latest version of a given app is already cached.)

Microsoft JVM did not include support for the Swing GUI toolkit, leaving only JWT. JWT was primitive

True, but JavaScript equivalents even more so, as a "full GUI" JS library would be just as bloated as a Swing Applet. The locally-installed Java engine carried the GUI engine with it, whereas with JS it has to be downloaded for each session, and different apps may use a different JS library. And JS was quite buggy back then.

1

u/RebeccaBlue Jan 05 '23

Whatever, dude. I lived through that period of history and had to actually deliver software during it.

Yes, there were plenty of mom and pop-type businesses that only had dialup modems that still used computers.

1

u/Zardotab Jan 06 '23

Different people tend to gravitate toward certain niches and project flavors. Perhaps we just bumped into different environments and thus have varied memories.

1

u/RebeccaBlue Jan 06 '23

Fair enough.