this post was submitted on 26 Dec 2023
33 points (67.7% liked)
Programming
17364 readers
198 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.