I linked to the anchor where it says that, right to the bottom of the section 4.3. Will people just STOP saying JavaScript was ‘never intended’ to have ‘nothing to do with Java’? They clearly meant JavaScript to be to Java what AWK is to C, at least syntax-wise. I was born one year after JS was conceived (the standard says ‘invented’, invented my ass! Who ‘invents’ a language?) so I am too young to have been around in the early days of web. But it seems like people back then wanted Java to be lingua franca of web, a bit like PostScript in the thread I posted a few hours ago. They named it JavaScript to assure people that it’s the interpreted, scripting form of Java.
Now don’t say ‘JS and Java are like car and carpet’ you will look like an idiot.
Also if you are wondering why I am reading the standard, it serves two purposes. First is, I wanna implement it one day in the future. Second is, I know shit about web scripting and I wanted to make myself a blog and I miserably failed. So I am learning it.
I know nobody asked, but one person might be wondering why someone would do this to himself.
JavaScript was created by Brendan Eich for the Netscape Browser. The job said to embed Java in the browser, but Eich was a Lisp guy and wished he could actually embed Scheme instead. Scheme is about as far as Java as one can get in terms of paradigm. Eich must have been stubborn because the result was JavaScript which is almost, but not quite, entirely unlike Java. Lulled by the seemingly familiar syntax, decades of coders have been baffled by the wild prototype-based object paradigm and the functional style hiding underneath.
JavaScript being somewhat like Java was an arbitrary constraint that was pushed by marketing and that was very partially honoured during implementation. The kinship between the two languages is slim at best. When explaining tech issues to the layperson, it’s important not to sweat the details and get to the point. Here the point is: JavaScript and Java are like car and carpet.
Also, chill. You have a lot to learn. We all do. Stop saying your colleagues look like idiots.
Good info dump. Can’t image S-Expressions in web dev today really. Also, I did not mean it maliciously, this is a stupid thing after all.
To be honest, XML can be considered to just be a more verbose version of s-expressions. It is easy to convert between XML and SXML.
Verbose and ugly! Btw, check out this S-Expression parser in C I wrote several months back: https://gist.github.com/Chubek/d2f0ac9067521716d2ab31c93948e885
It’s truly *easy to parse them!
No biggie! The birth of JS is told in numerous different places (and ways) on the net, if you’re curious you should definitely look it up.