Honestly, mainly just due to our existing familiarity with Rails and its huge ecosystem. We knew we'd be carrying out a wide array of tasks on the server, and there's a gem for everything.
I know this is largely true for the Node/Typescript ecosystem as well, but I've personally found Rails to be more plug-and-play.
They’re probably about equal when it comes to availability of plug n’ play libraries. Note: a lot of teams find that they’re more productive when they can use the same language throughout the whole stack.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I’m so glad to see you recommending Next and TypeScript. Why not TypeScript on the backend too?
Honestly, mainly just due to our existing familiarity with Rails and its huge ecosystem. We knew we'd be carrying out a wide array of tasks on the server, and there's a gem for everything.
I know this is largely true for the Node/Typescript ecosystem as well, but I've personally found Rails to be more plug-and-play.
They’re probably about equal when it comes to availability of plug n’ play libraries. Note: a lot of teams find that they’re more productive when they can use the same language throughout the whole stack.