I sense that I've touched a nerve and I'm sorry for that. May I ask what you believe I'm gatekeeping?
> It's also wrong, since Deno removes many idiosyncrasies about server-side JavaScript.
Could you offer some examples, so that I can learn?
I would agree with your statement that Deno removes idiosyncrasies of server-side JavaScript, but that's when viewed from a front-end-first perspective (ie. the predominant and perfectly reasonable perspective of code camp graduates that I've worked with).
That sounded a bit like the "imigrants stealing our jobs" argument.
"Deno removes idiosyncrasies of server-side JavaScript, but that's when viewed from a front-end-first perspective"
Not just the frontend perspective, but also the ECMAScript perspective, in which even Node.js creators participate.
I see that, thank you. Perhaps it would have helped if I'd added the word "experience" to the end.
I sense that Deno is primarily being pushed by developers who [graduated from] React-based code camps who are (understandably) looking for a wave to ride [toward] "full stack" software development [experience].
> but also the ECMAScript perspective, in which even Node.js creators participate.
Could you point me to concrete examples?
No, this is the gatekeeping mentality of many people software development.
It's also wrong, since Deno removes many idiosyncrasies about server-side JavaScript.