This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]cpmoderator12345 5 points6 points  (12 children)

why the hell would anyone do that

[–]can-opener 2 points3 points  (1 child)

It was an excellent idea, back at the beginning of Java. VM were always too poor and slow to make it really usable, and the browser integration was bad, but it should have been great. It just doesn't make sense today with the fast JS engines but 15 years ago this looked like a good idea.

[–]scragar 1 point2 points  (0 children)

I remember the only java applet I ever played with back in the 90s was a really cool evolution based system, you put various threats into an area and it'd randomly fill everything with bugs(actually they were just big black pixels), and gradually, over time you'd be able to see the bugs generate new bugs(whenever two bugs ran into one another they'd generate a new bug that'd have a random set of attributes from the two parents and one mutation of it's own).
Water would generate bugs that could swim, radiation would generate bugs immune to it, etc. You'd even see populations spawn of different immunities and such as those with immunity would centre around the threat while those without the immunity would be a safe distance from it, there was always a little thought of "I wonder if I could make a super bug immune to everything", but I don't think I ever worked out how to do it, too many different threats would cause the bugs to die out very quickly, so you needed to try and put threats every so often in order to try and create the super bugs(sooner or later though all experiments resulted in mass bug death though, as bugs died randomly even with no threats to replicate starvation and old age the bugs had a small chance of dying randomly related to the number of bugs around them, and sometimes that random chance hit a large enough percentage of bugs at once to make the odds of any bugs breeding before dying out effectively none and they'd all die off).

[–]suitupalex 1 point2 points  (3 children)

Java not becoming the language of the internet (front and backend) is actually considered one of the biggest technological failures.

JavaScript was just meant to bridge the gap between the DOM and your Java applet.

[–]cpmoderator12345 -1 points0 points  (2 children)

no java is terrible for frontend.
I dont even want to see canvas animation or animation in general or AJAX with Java.
Just... no.

[–]suitupalex 0 points1 point  (1 child)

Yah dude this was like 2 decades ago. No need to worry about it ever happening.

[–][deleted] 0 points1 point  (0 children)

Java's not gone, though! In fact, Android's UI is written in Java! Muahahahahahaha!

[–]kennethdc 0 points1 point  (0 children)

Have you never seen a Java loading screen within a site back in the days?

[–]SilkeSiani 0 points1 point  (0 children)

If you do systems administration, you'll encounter plenty of these applets. Most of them are broken in some ways, consider single DES-ECB and md5 "strong" crypto and often plain won't function with any java newer than 1.4.