In my experience, the documentation for Rails is less helpful than the documentation for Django along every imaginable axis. Why is this?
-
-
Replying to @inglesp
The Rails guides are full of references to classes and methods and options with no links to further documentation...
1 reply 0 retweets 0 likes -
Replying to @inglesp
...so you end up googling and can only find internal API docs which tell you nothing useful about how to actually get stuff done.
1 reply 0 retweets 0 likes -
Replying to @inglesp
Case in point: can anyone tell me what http://apidock.com/rails/ActiveRecord/ConnectionAdapters/SchemaStatements/add_reference … does or how I use it?
2 replies 0 retweets 0 likes -
Replying to @inglesp
Contrast this with the Django docs on migrations: there's a detailed introduction, and there's handy comprehensive reference material too.
2 replies 0 retweets 0 likes -
Replying to @inglesp
As a result, when beginners ask me whether they should learn Django or Rails, I can only recommend Django.
1 reply 0 retweets 0 likes -
Replying to @inglesp
Learning to code is already hard -- and doing so with poor documentation is so much harder.
1 reply 0 retweets 1 like -
Replying to @inglesp
So why is the Django documentation so good? Is it technical? Cultural? Was it baked in from the start?
3 replies 0 retweets 0 likes -
Replying to @inglesp
@inglesp I really don't think it's a Django thing. Compare these - https://docs.python.org/3/library/index.html … http://ruby-doc.org/stdlib-2.3.0/ https://docs.oracle.com/javase/8/docs/api/ …1 reply 0 retweets 1 like -
Replying to @davbo
@inglesp I think@rustlang are doing an excellent job too - https://doc.rust-lang.org/std/3 replies 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.