3 ms·
Rails is what pays the bills :) Just because I don't like _parts_ of Rails doesn't mean I will completely abandon it. This occurs in other parts of my life too.
by ryanbigg 4y ago
Rails is what pays the bills :) Just because I don't like _parts_ of Rails doesn't mean I will completely abandon it. This occurs in other parts of my life too. I find it really inefficient to use allen keys to tighten hex screws, so I recently bought a set of hex heads. Now I can use them with my screwdriver. Doesn't mean that I've sworn off allen keys altogether though, because sometimes they come in handy in particular circumstances.
I just use the right tool for the job, and in this place I do not think strong parameters is the right tool for the job.
- Fire-Dragon-DoL 4y agoGlad to see you here! You helped me a lot 10 (more? Lost track) years ago on IRC, when getting started with Rails, as well as by reading "multitenancy with Rails". Indeed, Rails pays the bills. And pulling out companies from the trouble they are in due to common Rails misuse is still very rewarding. Haven't yet figured out how to help companies deep into callback hell though. Might be non-solvable.
- sparker72678 4y agoTo each their own. It was dickish of me to say, "it seems like he’d be a lot happier with something that isn’t Rails." For that, I'm sorry. The dry-rb approach isn't for me. That doesn't mean it's not going to resonate with a lot of others. (Clearly, it does) To me, the Dry Schema approach feels unnecessarily heavy-handed and duplicates work that I would expect to be done in the model. Strong Parameters helps a bit with form data safety, but I'm not looking for anything else out of it. I'm expecting my models to validate and coerce those strings into something useful, and raise errors if the data is invalid. Dry Schema feels like an unnecessary layer in the middle. ¯\_(ツ)_/¯