|
|
|
|
|
|
by rahen
1018 days ago
|
|
|
How would you sell Node to other old guys? Especially compared to Go. I try to favor simple, efficient software. I used to dislike PHP because it was so messy and inefficient, until newer frameworks like Django made it look like it was slim and snappy.
Maybe, in this race to the bottom, Node stands out in a way I hadn't seen, so I'm genuinely interested. |
|
|
JavaScript has a huge business case in the front-end. Going another direction is possible, but you're really fighting against the grain to do so.
Go node/bun/deno and you can build back-end and front-end with one language. This has pretty significant advantages. Particularly if your goal is small teams (or solo) with "full stack" style devs. There are fewer siloed specialists required in the org.
Language concepts, syntax and patterns are a significant part of the cognitive load needed to develop.
If you're in a siloed org with specialists anyway, there is minimal draw.
I've done things like have a backend I brought into the front end to mock an immature system. Shared code between the back end and front end for offline-first systems. You just can't do that kind of stuff when you don't share a language between front-end/back-end.