2 ms·
> The kind of magic where you're given some functions to call, and some places to put your code, and if you ask why, you are told that you don't want to know, s
by jdminhbg 10y ago
> The kind of magic where you're given some functions to call, and some places to put your code, and if you ask why, you are told that you don't want to know, so shut up.
Rails is open-source and extensively documented. I honestly cannot understand this take at all.
- qwertyuiop924 10y agoOkay, YES, Rails had docs, but that's the attitude I see: use this, do this, put your code here, we know best. The docs do not ENCOURAGE understanding of how Rails works, or why it is the way it is.
- jdminhbg 10y agoThere are plenty of docs (official and unofficial) explaining the internals of how and why Rails works; here's an example: http://guides.rubyonrails.org/initialization.html http://guides.rubyonrails.org/initialization.html The documentation for getting a blog built in 15 minutes doesn't explain why you put your code in each place or how it's put together, because that's not the point. Rails is about making default decisions for commonly bikeshedded questions like "how do we name our database tables" so you don't waste mental bandwidth on them when you're trying to build an application. But explanations for how and why all that happens is very readily available.
- qwertyuiop924 10y agoFair 'nuff. Sorry.
- twblalock 10y agoRead the code, then. The docs are for people who want to get stuff up and running. The code itself is what you should read when you want to understand how anything really works.
- qwertyuiop924 10y agoI shouldn't have to read the code to be able to basically reason about what my app is doing. I don't necessarily want to know EVERYTHING, but I want to know the basics of what's going on.