this post was submitted on 23 Mar 2026
18 points (87.5% liked)
Programming
26193 readers
203 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Same goes for any application that are proud to use "no framework". It just means that you partially implemented your own poorly documented half-assed framework.
It's a little more nuanced than that.
I will gladly write my own small, half-assed framework that I 100% know, can reason about, can debug, and can extend to fit my requirements. I will gladly pass on a fat-assed, bloated framework with a million dependencies, where I only need a few features, and where if I need something that isn't offered by the framework I have to submit a PR or add some janky-ass workaround.
That is fine for your personal projects. It stops being fine as soon as you need to hire extra people and grow the team.
Why though?