3 ms·
Why don't you have a tight correspondence, though? Is it something intrinsic in the problem space, or you just want to do it the way you think of it? In a numb
by beat 8y ago
Why don't you have a tight correspondence, though? Is it something intrinsic in the problem space, or you just want to do it the way you think of it?
In a number of cases, I've found that the Rails Way was smarter than my original assumptions.
- village-idiot 8y ago... because not everything needs it? If you’re mostly writing CRUD apps, you’re correct. But the world is not all CRUD, even if you’re only looking at the web space.
- beat 8y agoSo at some point, you have to ask yourself if the headache of working around something Rails doesn't do well is worth throwing Rails out completely over. Can it be tossed off to a microservice and routed away in nginx or whatever? Does it really not suit the Active Record pattern? If you need a screwdriver, then stop complaining about how much your hammer sucks and get a screwdriver instead. Or ask yourself if a nail could work in the same situation.
- village-idiot 8y agoYeah, that was my point.
- Daishiman 8y agoSo what exactly are those correspondences that don't match? Because in a decade of web dev I have not really seen a satisfactory counterexample. Fundamentally everything lives in a request-response cycle and almost everything you load comes from a DB or as a file asset.