3 ms·
I'm happy I don't have to deal with these paradigms day to day anymore: - Making everything go through a "controller" instead of well designed clients and APIs
by stevebmark 6y ago
I'm happy I don't have to deal with these paradigms day to day anymore:
- Making everything go through a "controller" instead of well designed clients and APIs. Mixing rendering, redirection, ajax handling as well as page serving as well as business logic all into a "controller" is painful. ("Models" and the spaghetti design patterns they come with are even worse)
- PHP style templates that trigger database queries inline, making them difficult and eventually impossible to optimize
- Scattering view code across random places instead of writing view code with its corresponding view logic in the same file/component
- Wiring up functionality to templates by targeting selectors
- Manually setting innerHTML for dynamic functionality
- Dealing with rails "turbo" anything, which is not useful in a real world application, and dangerous (we've had production outages because of trying to use turbolinks)
- Not being able to customize behavior because you're locked into Rails design limitations
- jypepin 6y agoI agree. I love Rails and think that it was beautifully designed for its purpose, but it's absolute hell once you start trying to integrate React and more complex frontend stuff into it through its view system (vs using it as an API and have a separate frontend).
- albertgoeswoof 6y agoYou’re probably going to end up doing all those things anyway- just inventing it yourself instead of following a convention
- aantix 6y agoWhat happened with the outage and Turbolinks?
- strzibny 6y agoInterested as well.