Not an affront; we just seem to have a surprisingly different notion of a React bootcamp graduate. It requires both the respect for web standards and the annoyance with Node's quirks to have an appreciation for Deno, neither of which a recent React bootcamp graduate would have had the time to cultivate. Whereas, since such hypothetical graduate is more likely to be in search of immediate practical in-demand skills, they would be more likely to pick Node over Deno as a much more popular option. Plus, they would be likely to have been exposed to Node during their bootcamp training, by running webpack, create-react-app, and suchlike.
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.