3 ms·

I can't stand answers like this ... why is it a "garbage tool?"

• csense 13y ago
  My main complaint: The syntax is awful [1]. The runtime is also extremely bloated. To run one fairly simple web application with a handful of users, Rails uses well over 500 MB. I have no idea what it could possibly be doing with that much memory -- is it trying to make a separate object for every pixel? Startup for Ruby apps often takes over a minute. Ruby is Rails. It's hard to find information about using Ruby for non-Rails projects. So as a beginner, not only do you have Ruby's weirdness to deal with, you're often fighting the number of moving parts in a modern web application. Also, "magic." I haven't used Rails enough to know about this, but I hear "magic" is common, e.g. (I've heard) Rake uses some horrible hack to monkey patch the lexer or somesuch so it can have its own syntax. This kind of thing leads to code that's even harder to understand because you now have non-local dependencies. To be fair, Python also allows monkey patching, but also has a strong "don't-do-that" cultural norm. [1] https://news.ycombinator.com/item?id=5872899 https://news.ycombinator.com/item?id=5872899
  • dham 13y ago
    Rails is not bloated, it just comes with a lot of features. I'd suggest watching these videos. http://www.youtube.com/watch?v=2Ex8EEv-WPs http://www.youtube.com/watch?v=2Ex8EEv-WPs http://www.youtube.com/watch?v=uUNdKVG2W-8 http://www.youtube.com/watch?v=uUNdKVG2W-8 A typical Rails instance will use 100 - 150mb, and does not take a minute to start up. Have you actually used Rails? I have several large projects and none have ever taken that long to startup. I use Ruby for non Rails projects all the time and had no issue finding how to include Active Record and Action Mailer into a Ruby CLI application.