Programming

17420 readers

31 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

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 [email protected]

founded 1 year ago

MODERATORS

[email protected]

Here are 20 reasons why frameworks make us lousy programmers (chat-to.dev)

submitted 10 months ago by [email protected] to c/[email protected]

28 comments fedilink hide all child comments

It is not accurate to claim that frameworks automatically make programmers bad. In fact, frameworks are powerful tools that can accelerate development, promote best practices, and facilitate code maintenance. However, it can be argued that overly relying on frameworks without understanding the underlying principles of programming may have some negative effects. Here are some reasons why this might happen:

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 10 months ago

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)