3 ms·

What problem are you having with Rails currently? A lot depends on that. Personally, I’ve found that API/SPA apps end up being more development work per new fe

What problem are you having with Rails currently? A lot depends on that. Personally, I’ve found that API/SPA apps end up being more development work per new feature than a single Rails monolith. Also, anything you switch to is going to feel a lot more productive at first. This is somewhat deceptive, because what your really seeing is that your new software codebase is solving a much smaller problem at first, and of course that's much easier to work with.

kh3dr0n 8y ago
The current app is huge and has a lot of legacy/messy code, that still running, changing it will be really hard now. Tests takes ages to finish, the initial project structure is bad, many mistakes were done in the past. We are planing to build huge new feature, that can has it own UI, So we decided to go for SPA, but where are asking ourselves what's the best way to build the API, Just build it on top of the current project or new project with Rails or other stack ?!
- fiedzia 8y ago
  You screw up your architecture and development process. Choosing your stack is not what you should focus on, whatever you choose will not solve your problems.