> You can still have separate codebases for server and client in JS/TS...
Indeed, but unlike Go/Python (backend) and TS/JS (frontend), the separation is surmountable, and the push to "reuse" is high.
> and the push to "reuse" is high
Other than types and stuff like zod validators there's not a lot of overlap between server and client code.
I agree with your point that iso code can be confusing. But beyond that I think you're just pushing an irrational anti JS narrative.
> and the push to "reuse" is high
Other than types and stuff like zod validators there's not a lot of overlap between server and client code.
I agree with your point that iso code can be confusing. But beyond that I think you're just pushing an irrational anti JS narrative.