2 ms·
Someone once told me "If you're not using a framework, you're building one". I thought a lot about the many implications of that sentence, one of which is rele
by dusted 5y ago
Someone once told me "If you're not using a framework, you're building one".
I thought a lot about the many implications of that sentence, one of which is relevant for this article. Understand that you _WILL_ always use a framework, whether it's an external one or your own. Knowing this, when choosing not to use an external framework, you must show consideration to the design of the one you're inevitably building, and chose to build it intently, rather than by accident.
I'm entirely in agreement with every sentiment of this article, not only does it make software that will last longer, but for some of us at least, makes for a much more fun, interesting and enjoyable development experience.
Writing a program from scratch actually feels like programming, it feels like doing the thing we're here to do, rather than laying the plumbing that ties together a multitude of third party, constantly-changing (if not just randomly disappearing from the internet) frameworks together.
- dragonsky67 5y agoI think the point that the article was making is that if you don't use a framework, even if you make your own, then you can select the libraries you are using by how supported they are. The other point about building your own "framework" is that you can reduce the library count significantly. You don't need to include a library you only need one function from... Just reimplement that function in your own code.