101–110 of 476 posts
What bothers me is that they actually never apologised. A simple statement of acknowledging the damage caused would do!
I assume you have never used VBScript, which was the major alternative back then.
I wish Matz had been there with Rubyscript. JS wasn’t as powerful back then; it took over a decade for it to evolve enough where people would really use it for much other than client-side validation and neat UI tricks. In comparison, Ruby was a great language to use, and it would’ve grown more quickly.
What bothers me is that they actually never apologised. A simple statement of acknowledging the damage caused would do!
I still don't know why they stuck the "Java" name on JavaScript. Very confusing when the two languages are completely unrelated. > Java programs and JavaScript scripts are designed to run on both clients and servers, with JavaScript scripts used to modify the properties and behavior of Java objects, so the range of live online applications that dynamically present information to and interact with users over enterpris…
Partly marketing but the integration certainly existed. As I recall, public methods in the main applet class are exposed to JavaScript. It was a little slow and clunky but it worked. The idea was similar to how web components are used today. Your web page would contain custom applets for a fancy input field, a calendar control date picker, and whatever other controls html didn’t provide, all implemented as Applets. I…
Was it JVM startup time, Java xfactory-begat-y-begat-z code init time, what?
Also, applets run outside the browser, correct? I.e. on the browser's host system in a separate JVM process?
Nothing technically wrong with Java and JS of course, but this terrible PR piece which desperately tries to pitch Java as an integral part of the web, going even as far as naming an innocent scripting language for web browsers JAVA script truly demonstrates that the mid-to-end-90's were the dark age of computing (at least the corporate side).
It was actually a fairly exciting time...? OOP had really just broken into the mainstream (with Java, the first OOP to really take off) and would go on to become ubiquitous, spawning tons of little new languages (including Python). There were multiple vendors pushing VB-like products, some arguably better than MS itself, giving high levels of productivity (who some argue have never been achieved since). PCs had drama…
What bothers me is that they actually never apologised. A simple statement of acknowledging the damage caused would do!
I think they understand the repercussions. Imagine if you said that the pain and suffering of every developer for the last 25 years was largely your fault. There would be lawsuits. Class action. We'd all travel to come testify.
Hyperbole and nonsense. No one was "suffering" under Javascript until Node and compile-to-js languages and the Byzantine nightmare of a development environment that they created came along. No one was shouting "Javascript Delenda Est" when all you needed was an FTP account and a text editor to configure a JQuery plugin.
I mean, Javascript development used to be reasonably simple, straightforward and fun. It's Silicon Valley's fault that it no longer is, not the language.
I recall being at a local (Detroit) IT seminar around the time Javascript was announced, and some guy from Sun with an English accent going on and on about how safe javascript would be, since it couldn't access local resources and they had purposefully left out a lot of functions that could compromise the user. It's changed a bit since then, I'd say.
Being limited but safe may be the reason that JavaScript has won out over Java. As I recall, applets turned out to be a security nightmare.
ActiveX was winning, but that really was a security nightmare.
Eventually enough of the useful parts of ActiveX crept into JS enough to build real stuff with it.
> JavaScript is analogous to Visual Basic in that it can be used by people with little or no programming experience to quickly construct complex applications. >JavaScript scripts are designed to run on both clients and servers, with JavaScript scripts used to modify the properties and behavior of Java objects, so the range of live online applications that dynamically present information to and interact with users ove…
... has it? ;-)
(Note: joke with deference to the huge pool of incredibly talented js developers! But there are still a lot of mind bogglingly terrible js devs too)
What bothers me is that they actually never apologised. A simple statement of acknowledging the damage caused would do!
Stay mad, guys! :)