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.
Would an experienced Java developer that has never touched JavaScript before know how to use JavaScript well enough to use it in a professional application without having to learn/revise a lot of things?
Would an experienced JavaScript developer that has never touched Java before know how to use Java well enough to use it in a professional application without having to learn/revise a lot of things?
No and No - They are like car and carpet. Unlike something like C and C++ or JavaScript and TypeScript that you can easily adapt to in a relatively small amount of time, Java and JavaScript serve completely different use cases and require significantly different skillsets.
Ugh I think the gap between c and c++ is wider than between java and Javascript, but admittedly I haven’t done much of the latter two
You can take the contents of a C file, put it into a C++ file and there’s an 80% chance it will work without modification, and 15% of the incompatibility will be just sticking a type on your pointer instead of using void pointers (untyped pointers), or in newer code switching the restrict keyword for one of C++'s newer pointers.
You can’t do that between JS and Java.
Douglas Crockford, author of “JavaScript: The Good Parts” has said:
“JavaScript is the only language in the world that people think they write without learning it first.”
I think this is a true statement (well, that and bash).