Stack matters a lot if the project is open-source. We migrated ToolJet's backend from Rails to node after the beta launch last year. We've documented the thoughts behind out decision here: https://blog.tooljet.com/migrating-toojet-from-ruby-on-rails....
The benefits that we got:
- Contributions from around 200 contributors so far.
- We built a plugin system and plugin development kit that helps community build plugins for ToolJet.
ToolJet anyway is extendable via JS ( use JS anywhere on editor, run custom JS snippets, bring your own React components, etc ), stack also being 100% JS/TS made sense for us.
The benefits that we got: - Contributions from around 200 contributors so far. - We built a plugin system and plugin development kit that helps community build plugins for ToolJet.
ToolJet anyway is extendable via JS ( use JS anywhere on editor, run custom JS snippets, bring your own React components, etc ), stack also being 100% JS/TS made sense for us.