[SamInTheShell]

I'm kinda in the camp of wanting nothing to do with node if I'm building in Go. We have our own stdlibs for serving.

[pjmlp]

I am on the Java/.NET camp for the most part, however I do share the sentiment.

[throw1234567891]

I’m in the other camp. I switched to node backends from go because of vite.

[indemnity]

Same, hard pass on remote shell as a service that is Node and its ecosystem.

[jackielii]

I'm not sure I follow. Node is not on the production path

[evilduck]

It's easy to follow, it's a knee jerk tribalism reaction and not a logical or informed one. Go attracts backend or anti-frontend people so anything intermingling the two will draw out the commenters who bemoan anything that realistically builds a modern website. Just ignore it, your choice for dev tooling is practical and makes sense to me.