3 ms·
> Which is something we came to accept and assume for interpreted languages (Python, Ruby, Node, etc.) Tangential, but: - "Node" isn't a language, it's a JS r
by joepie91_ 5y ago
> Which is something we came to accept and assume for interpreted languages (Python, Ruby, Node, etc.)
Tangential, but:
- "Node" isn't a language, it's a JS runtime
- There's no such thing as an "interpreted language", whether something is interpreted or not is a property of the execution environment, not of the language itself
- The commonly-used runtimes for JS at least are JIT compilers, not "interpreters", and this can be true for some Python/Ruby runtimes too
- j1elo 5y agoI didn't downvote your comment. But I guess some people did, possibly because you did the thing about stating several facts where all were true but none were relevant. I'd swear I read that this phenomenon even has a proper name but cannot recall it right now. (And for the record I know very well about the internals and technicalities about the words and names that I used: Node.js is the de-facto Javascript runtime for the backend, popular to the point that people commonly refer to it as "programming in Node"; Python and Ruby are just languages but their majority of users run their program with the default official interpreter, so through a metonymy we can refer to either even when actually talking of the other; and etc. For economy of the language and avoiding the pedantry, I grounded my comment on the most generally perceived notion about those technologies. You see, just to avoid unnecessarily long explanations like this one)