Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yup, java just didn't actually do it very well.

Or java was too heavy for the computers at the time to get people to use "applets" for everyday things (i.e. go to a new website a do a thing on it)

Flash et al also failed to catch for long.

The web browser's success might have something to do with neverending feature creep as opposed to "this can do everything but as such it's broken and vulnerable".



Applets implementations were terrible - the problem wasn't so much Java ( though early versions pre-jit were slow ) , but the interface between the browser and the applet.

Memory leaks abounded in particular.

Life cycle management was difficult as well.

Note the interface had to be implemented in each and every browser separately - compounding the problem - for applets to be viable it had to work on all the major browsers well.

Not blaming the people who worked on it - I suspect the origin design was put together in a rush, and the work under-resourced, and it required coordination of multiple parties.


Java's constant security nightmares and lack of integration into browsers was the bigger problem, IMHO.


Also you had to install runtime vs browser which is bundled every OS.


I think everyone instinctively knew that “once it is in the browser it cannot fail”, so it has been a schelling point for tech.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: