3 ms·
I'm not sure what sort of case the author intends to make here. If he's saying Rails isn't the best fit for all possible projects, that's blindingly obvious. If
by Zak 19y ago
I'm not sure what sort of case the author intends to make here. If he's saying Rails isn't the best fit for all possible projects, that's blindingly obvious. If he's saying you should think twice before using Rails when it is a good fit, most of his arguments don't apply.
The one I do think needs some confronting is the "no throat to choke" argument. It's just silly: if you research any sufficiently popular tool, you'll find out what areas it falls short in. If you aren't able to work around the problem as easily as you thought, you'll end up with delays and bugs. With a vendor supported product, you can choke your vendor rep until he helps you solve your problem. This usually takes as long or longer than fixing it yourself, and the result is the same: your project is still late and buggy.