I’ve seen this type of thing in vanilla js vs react projects. Where there was a fine vanilla js implementation, but it was abandoned by maintainers to do a reac

I’ve seen this type of thing in vanilla js vs react projects. Where there was a fine vanilla js implementation, but it was abandoned by maintainers to do a react version. Or a new frontend package is built for react by default rather than vanilla js, (or a very light set of js dependencies) even if it easily could have been. And my experience is that react has been corruptive to the vanilla js ecosystem as a result. It’s a bit of a reverse from node->deno but I could easily see how deno would be stunted or affected in an unknown but possibly not great way by this. All that said, Deno has had to pivot because node seems to have gotten its act together to some extent. At least compared to when Deno set out. So as a practical user acquisition need, not want but need, Deno had no choice but to do this. And the decision to go down this path was made quite a while back, iirc. I remain hopeful for Deno and the team behind it. Frontend tech is very competitive. The thrashing across the frontend stack that backend folks recoil from has made things stronger and there’s a lot of talent at work.