3 ms·
I’d say the biggest drawback is performance. Ruby is slow and resource hungry, Rails leans heavily on reflection. Starting a large Rails app can take 10+ second
by alxmng 4y ago
I’d say the biggest drawback is performance. Ruby is slow and resource hungry, Rails leans heavily on reflection. Starting a large Rails app can take 10+ seconds (even with bootsnap). Large test suites can become time consuming to run. Heavy use of partials can noticeably impact rendering time.
However, this is not an issue until you have a large app. It’s a small downside compared to the upside. It’s also less of an issue today as servers have become cheaper and more powerful. As DHH said, “…sure, I'd like free CPU cycles too. I just happen to care much more about free developer cycles and am willing to trade the former for the latter."
- NayamAmarshe 4y agoThanks for the reply. I guess it's not as big of an issue if it can save development time. > Rails leans heavily on reflection. Starting a large Rails app can take 10+ seconds This is nothing compared to the spring boot project at my job, takes like a whole minute to start haha
- Okawari 4y agoIf I may ask, how big is that project?
- NayamAmarshe 4y agoWell, it's a business software so a lot of moving parts (but that's also because it's Java and there's a lot of code for not a lot of functionality). I'm not a spring boot pro or anything but I think it's also slow because there are faults in the project. Stuff breaks often, hot reload is a mess and doesn't even work and there's no unit testing.