Yeah 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

Yeah 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.