zlacker

>>pavela+(OP)
I actually think that people should rather use EcmaScript name instead of JavaScript, because it's a way better name (much less confusing, given that this lang doesn't have anything to do with Java anyway). I wish Oracle started suing people to force everyone to use the better name.

>>siwata+Yc
The irony is I belive the JavaScript creator wtnted to latch to Java's popularity to called it JavaScript and now both Java and JavaScript are owned by Oracle and they want the name but not want to change is to ECMAScript, it's real official name.

>>suyash+gh
If you read the original JavaScript press release ( https://web.archive.org/web/20020808041248/http://wp.netscap... ), it's mainly intended as a language to write glue code so Java applets (where the real application logic would go) can interact with a webpage:

> With JavaScript, an HTML page might contain an intelligent form that performs loan payment or currency exchange calculations right on the client in response to user input. A multimedia weather forecast applet written in Java can be scripted by JavaScript to display appropriate images and sounds based on the current weather readings in a region. A server-side JavaScript script might pull data out of a relational database and format it in HTML on the fly. A page might contain JavaScript scripts that run on both the client and the server. On the server, the scripts might dynamically compose and format HTML content based on user preferences stored in a relational database, and on the client, the scripts would glue together an assortment of Java applets and HTML form elements into a live interactive user interface for specifying a net-wide search for information.

> "Programmers have been overwhelmingly enthusiastic about Java because it was designed from the ground up for the Internet. JavaScript is a natural fit, since it's also designed for the Internet and Unicode-based worldwide use," said Bill Joy, co-founder and vice president of research at Sun. "JavaScript will be the most effective method to connect HTML-based content to Java applets."

This was all actually implemented. JavaScript functions could call Java applet methods and vice versa (see https://docs.oracle.com/javase/8/docs/technotes/guides/deplo... ). Of course over time everyone abandoned applets because of all the security problems, and JavaScript became a good enough language to write application logic directly in it. Still, there's more meaning behind the name than it just being a cynical marketing move.

>>ndiddy+Ct
The language now called Groovy would have been JavaScript if the name wasn’t already taken.

>>mikepu+Ww
Haha completely agree, it is the "scripting language" made in the image of Java! It's a great language by the way!

>>brabel+ZB
There was also beanshell if you remember, of course never as polished nor adopted like groovy but it was also fun to use.

>>nunobr+zH
Is groovy actually really "adopted" much of anywhere? I feel like for 99% of normal people, their only real exposure to it is as the DSL of gradle and jenkins.

I can't imagine writing anything of substance primarily in groovy.

>>mikepu+zN
>I can't imagine writing anything of substance primarily in groovy.

That's solely based on a poor imagination, not trying...