Re:Don't make me think, or why I switched to Rails from Java...
by atmosx on Friday February 04, 2022 @01:00PM
(#30210250)
Apparently people prefer blog posts to docs. This is not a problem of course, until you need to either debug (hence understand what you're doing at depth) or build something non-trivial.
Re:Don't make me think, or why I switched to Rails from Java...
by space_fountain on Friday February 04, 2022 @01:38PM
(#30211031)
The problem with Rails is not a lack of blog posts or docs, it's that there's often no way to find what doc you need to read without already understanding the framework. Reading the entire docs and then trying to remember and understand it is a style under which some people learn well and I think it is important for mastery, but the ability to trace back and understand a small piece of a framework is valuable too especially when you're first starting out. Certainly when I try to understand something with node or js libraries I don't jump to blog posts, but I am usually able to find what I need to google to to get the docs I want. That wasn't the case with rails when I was first starting
Re:Don't make me think, or why I switched to Rails from Java...
by machiaweliczny on Saturday February 05, 2022 @05:19PM
(#30226847)
No the real problem with Rails is autoimport and bad tooling that you can't jump to source easily. I would love rails if jump to definition worked well but it's deal breaker.
Re:Don't make me think, or why I switched to Rails from Java...
by jack_riminton on Friday February 04, 2022 @01:04PM
(#30210309)
Agree. Perhaps the original poster was struggling to get to grips with the MVC setup because beyond that Rails is pretty easy to understand
Sure there are bits of 'magic' but you could build an entire AirBnB clone before you'd need to dive into them
Rails docs are among the best I've ever used for a framework personally. They blow most things in the JS ecosystem out of the water.