I found it interesting that you recommended that students learn JS (and programming, if they don't know programming) in Node. I feel that I helped myself by practicing JS (as a person who already knew programming in other languages) in the REPL of a relatively retarded browser, instead of in that of Node. That told me what features of JS are new. Since then, I looked at "caniuse" and grew some confidence that the "new" features (e. g. .? and dynamic import(...)) will work in the environments that matter for most audiences I might want to address with a website. Nevertheless, I feel that having some historical context as to which features might not be supported tells me where we are today relative to recent advances in the tech.
Hey Jack! Thanks for the response and your experience. It's awesome that you learned through the REPL haha, as most people would get frustrated pretty quickly with it :)
I think the main reason I mentioned in Node is that it's way too easy to mix up what is in the DOM in the browser (querySelector, Events, Elements etc) with being part of Javascript (those are all not JS). Granted, it's also possible to do this with Node but you have to be a bit more deliberate to mix up the Node APIs with what's in vanilla JS 😃
I found it interesting that you recommended that students learn JS (and programming, if they don't know programming) in Node. I feel that I helped myself by practicing JS (as a person who already knew programming in other languages) in the REPL of a relatively retarded browser, instead of in that of Node. That told me what features of JS are new. Since then, I looked at "caniuse" and grew some confidence that the "new" features (e. g.
.?and dynamicimport(...)) will work in the environments that matter for most audiences I might want to address with a website. Nevertheless, I feel that having some historical context as to which features might not be supported tells me where we are today relative to recent advances in the tech.Nooder [OP] 1 points · Jan 2023
Hey Jack! Thanks for the response and your experience. It's awesome that you learned through the REPL haha, as most people would get frustrated pretty quickly with it :)
I think the main reason I mentioned in Node is that it's way too easy to mix up what is in the DOM in the browser (querySelector, Events, Elements etc) with being part of Javascript (those are all not JS). Granted, it's also possible to do this with Node but you have to be a bit more deliberate to mix up the Node APIs with what's in vanilla JS 😃
jack_waugh 1 points · Jan 2023
Yeah, I agree that keeping those things separate, in the mind of the learner, has value.