2 ms·
I'd second this. Rails is still probably the fastest way to get an MVP off the ground, and most of the time it's more than fast enough. You can get UX on par wi
by jsmith0295 10y ago
I'd second this. Rails is still probably the fastest way to get an MVP off the ground, and most of the time it's more than fast enough. You can get UX on par with a well done SPA almost entirely using server code with Turbolinks 5 + Action Cable, too.
- kowdermeister 10y agoThe fastest way to get an MVP off the ground is to use the tools you know best. It doesn't have to be Rails :)
- jsmith0295 10y agoYes, this is also usually true. But if you don't know tools that are particularly well suited for the job, or you just don't like them and are looking for something else to try, I would put Rails at the top of the list for productivity. (For most use cases)
- nathany 10y agoThe only problem is that you need to maintain and enhance that MVP for the next several years -- unless it's just a hackathon. I've spent way too much of my life trying to optimize Ruby performance and memory usage, switching from one web server to the next, then fixing threading issues in dependencies, and so on. It's not fun. All that upfront productivity is lost in the end. Quite happy to spend more time upfront investing in a reliable end-product.