3 ms·
When I first used Rails, I was frustrated by two main things: * Files everywhere! I like starting simple, and you generate all these folders with things I jus
by xiongchiamiov 16y ago
When I first used Rails, I was frustrated by two main things:
* Files everywhere! I like starting simple, and you generate all these folders with things I just don't want to deal with yet.
* Lots of things were implicit, making it difficult for a newbie to the framework to understand the flow (How do we get from the controller to the template? was one, I think).
Now, that was several years ago (a little over 3, now), and both Rails and I have changed. I've been waiting for Rails3 to give it another chance, but haven't found the right project yet.
My current gripes with Rails are this:
* DHH is a prick.
* It's damned difficult to find a good Ruby feed that doesn't get polluted with Rails stuff.
My first issue is, of course, not very valid, but I have to admit that it exists.
For the second one, yes, I program in Ruby (and love it!), but I'm not using Rails. Even when I do web development in Ruby, it's with Sinatra. So, I don't want to see your frackin' "Ruby tips" that are actually Rails tips!
</endrant>