4 ms·
Rails has plenty of critics. You just aren't looking hard enough. The most common criticisms are: it's slow and it has too much "magic." At the end of the day
by enraged_camel 10y ago
Rails has plenty of critics. You just aren't looking hard enough.
The most common criticisms are: it's slow and it has too much "magic."
At the end of the day, it comes down to this: every framework has its pros and cons. When you use a framework, you gain certain benefits but sacrifice certain things and have to conform to the framework's opinions. In the case of Rails, the primary benefit is extremely fast prototyping. But that's only possible because the framework hides a lot of complexity from you, which can bite you in the ass if you try to go outside its conventions.
- mh-cx 10y agoThis. One fine example is Gitlab: It's full of features and does many nifty things. But it's painfully slow and the developers now have a hard time trying to fix this. [1] https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&sort=id_desc&state=opened&utf8=%E2%9C%93&label_name%5B%5D=performance https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&sor...
- sytse 10y agoThe slowness is not due to Rails. It is mainly due to us not scaling up the infrastructure team fast enough and now having problems with the file serving backend. We're working on it in https://gitlab.com/gitlab-com/operations/issues/42 https://gitlab.com/gitlab-com/operations/issues/42