Re:Don't make me think, or why I switched to Rails from Java...
by jmondi on Friday February 04, 2022 @12:52PM
(#30210141)
Call me crazy, I’d just rather read the relevant section of code I am working on and be able to understand it from there, rather than first having to understand the entire universe.
[ Parent
| on HN ]
Re:Don't make me think, or why I switched to Rails from Java...
by givemeethekeys on Friday February 04, 2022 @01:33PM
(#30210959)
When working with a framework, it helps to understand the framework. Then, all the individual pieces make better sense. The advantage is that you only have to gain this understanding once.
Re:Don't make me think, or why I switched to Rails from Java...
by MadcapJake on Friday February 04, 2022 @02:33PM
(#30211762)
A framework is a social contract, if you will. The framework authors are taking on the onus of some complexity to give you a cleaner and easier to grok codebase. The tradeoff is that you do need to read the guides or you will be diving deep into framework internals whenever you want to understand some app level code.