|
|
|
|
|
by steego
2309 days ago
|
|
That's because they hadn't used it yet. :) In all seriousness, everyone was in on Java. Even Microsoft (Everyone was in on Java, even Microsoft (https://en.wikipedia.org/wiki/Visual_J%2B%2B). So most of us saw browser plugins and applets as the future, and some of those plug-ins were very impressive in those days. JavaScript was seen as a glue language to manipulate components built in better languages. We thought there was going to be a rich component marketplace that was going to be embedded in web pages. We didn't think we'd still be mucking around with HTML and DOM manipulations. |
|
It's not that JavaScript solved that, it's that it's built into the browser such that you can't really skip it. Like the Java and Flash engine, a web browser is also a fat bloated leaky client. However, if you toss the first two, you are then dealing with 1 fat client instead of 3 fat clients. It's easier to keep 1 FC up to date than 3.