fjfuvucucuc
Joined 3 years ago
Joined 3 years ago
For a business that has engineers to manage this day to day it's less of an issue. For building things you want to live online untouched for a decade it's just not an option.
Laravel is nice to build stuff fast in one particular way. It's awful to maintain and heaven forbid you have a different idea about how things should be done.
This thread is so cope.
It's so refreshing knowing that my websites auto update themselves and I never have to update them unless there is a legitimate reason to do so.
Backwards compatibility is the ONLY thing I care about in a framework. Life's too short to babysit some frameworks ideas of how my code should work ten years after building the damn thing.
Is "new stuff" easier work than maintaining old stuff? I always thought it was the other way around. I always give greenfield stuff to the juniors. They fuck it up I fix it. It's basically like using chatgpt.
Personally I don't associate it with the negative connotations you do. I associate it with the word trying.