4 ms·
> the only time node is the right tool for the job is if you have a team of JavaScript developers who can't learn another language I’d push back just a little
by MichaelNolan 3y ago
> the only time node is the right tool for the job is if you have a team of JavaScript developers who can't learn another language
I’d push back just a little on that. If you’re on a small team writing a small app, having the frontend and backend both be in js/ts, and in the same repo, can be a big help.
- maccard 3y agoYeah I made a very broad statement. I don't think the value in having your frontend and backend in the same language is there though. Your frontend _has_ to be js/ts, but your backend should be a language you know. If you've spent the last 10 years working with rails, then rails it is. If you know go, then go. If you know node, are on a small team with a tight timeline, then _maybe_, but honestly I think I'd still rather rails or go. Completely agree about the same repo though.