Re:When Should You Not Use Rails?
by aliante on Wednesday August 05, 2020 @04:15AM
(#24058400)
“I can’t be bothered to do anything properly. It must be a problem with Rails.”
[ Parent
| on HN ]
Re:When Should You Not Use Rails?
by yakshaving_jgt on Wednesday August 05, 2020 @04:29AM
(#24058499)
What does "properly" mean in this context?
All of my income is from my own software businesses. I used to try to do this with Ruby, and there were lots of problems. Now I do it with Haskell, and there are fewer problems. This ended up being a very good business decision for me.
What is the return on investment for me as a businessman on bothering to "do anything properly" when the resulting product is both cheaper to write and is more stable if I just use a better tool? What do I actually gain? Some kind of nerd-honour?
Re:When Should You Not Use Rails?
by AndrewDucker on Wednesday August 05, 2020 @04:20AM
(#24058428)
"I recognize that no human is fallible, so I use tools that don't assume infallibility"
Re:When Should You Not Use Rails?
by spanhandler on Wednesday August 05, 2020 @09:50AM
(#24060707)
Safety aside, I find going back to “guess the source of the meta magical pattern-named method” intolerable these days. Onboarding to, taking over, or pinch-hitting in a Rails codebase is miserable unless it’s tiny and perfectly maintained by developers with excellent judgement and taste—and of course this is almost never the case.