←back to thread

163 points John7878781 | 1 comments | | HN request time: 0.34s | source
Show context
whalesalad ◴[] No.43536031[source]

We have come full circle #applets

Twenty years ago running java in the browser would have just been called "using the internet"

replies(3): >>43536097 #>>43536305 #>>43538842 #
esafak ◴[] No.43536305[source]

Java Applets gave Java a bad name. Java was that thing that made web sites grind to a halt.

replies(1): >>43536644 #
SJC_Hacker ◴[] No.43536644[source]

If it had come out of Google or Microsoft maybe even Apple, the JRE would have been integrated into the browser much more efficiently and it would have been no slower than Javascript

But I don't remember Applets being particularly slow even back then, if you had a decent internet connection and they were written by a decent SDE

replies(2): >>43536723 #>>43537353 #
TOGoS ◴[] No.43536723[source]

I wrote a lot of applets back in the day for little graphics experiments and such, somewhat inspired by Ken Perlin's homepage[1]. I found that it's quite possible to make applets that load fast and run fast if you care about those things while building it and do some profiling. If you pull in hundreds of megabytes of libraries and trigger a GC every second then of course it will be slow.

[1] https://mrl.cs.nyu.edu/~perlin/

replies(1): >>43538100 #
1. freedomben ◴[] No.43538100[source]

Same. I built a lot of animations with applets back in the day and if you avoided dependencies (other than what ships with the JVM) and your code wasn't ridiculous, you could get some pretty damn good performance out of it (minus initial load time which did tend to be suboptimal, but manageable). Applets were a pain in many ways but I think the tech gets blamed unfairly for bad performance.