←back to thread

78 points pjmlp | 1 comments | | HN request time: 0s | source
Show context
kstrauser ◴[] No.46189780[source]
> In the 2000's, politics interfered and browser vendors removed plug-in support, instead preferring their own walled gardens and restricted sandboxes

That's one way to say it. The more common way was that users got tired of crappy plugins crashing their browsers, and browser devs got tired of endless complaints from their users.

It wasn't "politics" of any sort that made browsers sandbox everything. It was the insane number of crashes, out-of-memories, pegged CPUs, and security vulnerabilities that pushed things over the edge. You can only sit through so many dozens of Adobe 0-days before it starts to grate.

replies(8): >>46189829 #>>46189834 #>>46189952 #>>46190045 #>>46190066 #>>46190195 #>>46190485 #>>46198543 #
exDM69 ◴[] No.46189829[source]
Exactly.

Java was so buggy and had so many security issues about 20 years ago that my local authorities gave a security advisory to not install it at all in end user/home computers. That finally forced the hand of some banks to stop using it for online banking apps.

Flash also had a long run of security issues.

replies(3): >>46190042 #>>46190048 #>>46190193 #
cube00 ◴[] No.46190042[source]
> banks to stop using it for online banking apps

I never understood why so many banks flocked to building their online banking in applets when it wasn't like you needed anything more advanced than HTML to view balances and make transactions.

replies(3): >>46190168 #>>46190899 #>>46203573 #
1. elric ◴[] No.46190899[source]
I'm getting the impression you're conveniently ignoring how piss poor HTML/AJAX/JS capabilities were back then, or even how slow internet speeds were.

Applets could do things that JS could not. Some bank applets did client side crypto with keys that were on the device. Good luck doing that in JS back then. My bank's applet could cope with connection losses so I could queue a payment while dialup did it's thing.