I much prefer to have all my framework tools half-implemented with no searchable documentation by a guy who quit 6 months ago .
this post was submitted on 26 Dec 2023
36 points (67.3% liked)
Programming
18304 readers
301 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
So say we all.
Article title: Here are 20 reasons why frameworks make us lousy programmers
Article body: Frameworks don't make us lousy programmers
It's very annoying that if an article title seems interesting, that it's a bait-and-switch/clickbait.
I honestly don't click the ones that seem too amazing.
developing frameworks, on the other hand...
Because that's the alternative, anyways. People love to pretend that's not going to happen, but of course we all do that. Nothing as cool as building your own little meat framework.
Of course, by the time you leave, it's an undocumented nightmare that has 15+ calls for every single functionality, is so abstracted it'd make my Math professor blush and has more security holes (that no one even has a reporting mechanism for) than all the frameworks you could end up using together.
(Still love writing my own stuff! 😅)
I use it as a learning tool. When I was making my own framework it forced me to learn all the intricacies of the thing I was making the framework off. TBH it never saw any use in a project but the process of making it is a huge learning experience for me.
As someone who wanted to use an engine, I tinkered with a framework for a bit and immediately found myself in the beginnings of creating a framework for said framework.
And they almost got away with this obvious scam, but unluckily for them I didn't want to do stuff like that. They might've pulled it off if the particular thing I wanted was more straightforward.
IMO most "flashy" frameworks betray the principle of high cohesion. Importing a time library to handle timezones is a great idea. Importing a math library to calculate derivatives is common sense for good reason. But huge frameworks that change the entire way a language is written are ridiculous. I'm looking at you, Vue and Tailwind. I usually see these sorts of frameworks used by people who aren't qualified programmers and who don't know software architectures or best practices. In other words, the kinds of people who get promoted to management positions and tell us what frameworks to use.
(Typescript is awesome though)
frameworks are powerful tools that can accelerate development, promote best practices, and facilitate code maintenance.
Citation needed.
This feels like something that was written by an AI, except for the last sentence.
lousy and lazy