4 ms·
> That has been the reason I always avoid > huge frameworks like RoR. For others it is the reason to use huge frameworks like RoR. Because alternative is to
by rimantas 10y ago
> That has been the reason I always avoid
> huge frameworks like RoR.
For others it is the reason to use huge frameworks like RoR. Because alternative is to hunt obscure bugs in the framework you built yourself.
- nix0n 10y ago> Because alternative is to hunt obscure bugs in the framework you built yourself. That's a false dichotomy, there are also smaller frameworks available.
- mudbutt 10y agoFinding bugs for something you wrote yourself is easy because you WROTE it and can easily reason about what each method does, what data/methods does it have access to etc. etc. Anyways, I unfortunately work with Rails and I hate it. To me Rails stresses and encourages bad practices, everything has an implicit environment inherited from a massive hierarchy of classes with their own implicit environment that will only work if the current state of the app matches what each classes assumes it will be. Data changes and morphs during the initialization and creation of class instances causing shitty bugs. EVERYTHING needs careful consideration of all of these relations and class hierarchies before writing simple things. Everything is highly coupled and interwoven making a change one place break something somewhere else. Rails should be taught in Universities as a case study in the pitfalls of Object Oriented Design Also essentially all of the major players have left and moved on to new things. Most Ruby Gems haven't been updated in years!