It appears you've received this as some sort of afront. Everyone looks for a wave to ride toward the future and riding a wave is not undesirable. The Node wave has broken and is coming to a rest, slowly over time. Deno is a motion to create another. That's the natural order of things and it's okay.

> Deno is more appealing to seasoned web developers, who appreciate its conformity to modern web standards, the absence of Node quirks, and a better security.

It's interesting isn't it, because I offered my thoughts as someone who could be described as a seasoned web developer - they were just not the same as yours today.

No, this is the gatekeeping mentality of many people software development.

It's also wrong, since Deno removes many idiosyncrasies about server-side JavaScript.

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?