4 ms·
I actually don't like rails' convention over configuration school of thoughts. It makes everything implicit. For any large rails app it's difficult to reason ab
by fantasticsid 10y ago
I actually don't like rails' convention over configuration school of thoughts. It makes everything implicit. For any large rails app it's difficult to reason about how things are working, unless you learn all the conventions by heart (by the way, these conventions don't seem to be documented well)
- pmontra 10y agoIf you are a Rails developer you know all the conventions and they help you at finding code with only an editor and a file manager. No need of IDEs. It's very easy to learn a new application, unless the original developer wanted to be clever, which usually means that was one of his/her first Rails projects. However there are other school of thoughts and not everybody likes the Rails way. It's fair and it's a big world with space for every opinion and tool.
- fantasticsid 10y agoI never learned 'all conventions'. There are countless cases where I had to dig into source code to find out how a certain feature is working/how it works with another feature/when the abstraction does not work the way I want I guess being implicit just makes it harder to find out which part of abstraction is leaking when it happens.. But again I'm not a good rails programmer. I was just never a fan of how conventions play such a big part, and was not well documented.