4 ms·
1) "a lot of the concepts Rails supports are antiquated" ... 2) "Rails hasn't shown to be that adaptable to more modern front end trends" Would you mind elabo
by nocman 8y ago
1) "a lot of the concepts Rails supports are antiquated" ...
2) "Rails hasn't shown to be that adaptable to more modern front end trends"
Would you mind elaborating? What Rails concepts are "antiquated", and what "modern front end trends" does Rails not adapt to?
I've never done any Rails development, but understand the general idea of how it works, so I don't have any skin in the game. I'm just honestly curious about what you were referring to.
- stephenhuey 8y agoI imagine SPA trends with frameworks such as Angular are leading to the parent’s conclusion. However, you can still use SPA frameworks and just use Rails as an API, or you can take a step back and realize a large percentage of web apps still don’t need a complex SPA framework and might get enough front-end functionality out of something like Vue. In other words, many developers fall into the trap of choosing tools they prefer even when they may take more time to use and not provide enough business value. Plenty of web apps would ship faster if built with Rails and be just fine.