3 ms·
Please read the article before complaining… Key point IMHO: > They [frameworks] are very powerful tools, written in plain vanilla language and in a very gener
by fuzzy2 6y ago
Please read the article before complaining…
Key point IMHO:
> They [frameworks] are very powerful tools, written in plain vanilla language and in a very generic way, a fact that makes them great learning tools which can help anyone learn how to code without them. In order to know how and when you should use a particular framework you have to understand how frameworks work. Understanding the strengths and the constraints of each framework will enable you to make the right choice of a framework. Even more, it will be very clear when you don't need one at all. Grasping the concepts of how frameworks work behind the scenes will deepen your knowledge about the language itself. Knowing the framework's rationale will enable you to write better code for each specific problem you encounter.
I very much support this. Know your tools!
- undecisive 6y agoI think the problem is that the site seems a little confused about what it wants. I'd consider: > [we are] interested in developing applications without frameworks. ... and ... > nor we will ever create campaigns against frameworks to be in direct contradiction, yet these are in the very first paragraph. Reading this page, I'd take it as a rallying cry against useless libraries that could be replaced with a few of lines in your codebase that can be understood and changed and adapted, rather than depending on a generic unchangable external source. Reading the manifesto itself (following the github link) it sounds like a rallying cry against something else entirely - management-dictated technical decisions. But maybe the confusion is intentional. People will read into it what they want to see.