Somewhere in the middle. I generally avoid using plugins of any sort if I can avoid it, and prefer sane defaults over customization, but I also avoid software that comes bloated with features I’ll never use.
Respectfully, yes.
If it’s that local of an issue, why not just go around with a clipboard and piece of paper and talk to your neighbours about it? Modern technology isn’t always the solution, sometimes the tried and true methods are still valid for a reason.
Yeah, I stopped using Nvidia like 20 years ago. I think my last Nvidia card may have been a GeForce MX, then I switched to a Matrox card for a time before landing on ATI/AMD.
Back then AMD was only just starting their open source driver efforts so the “good” driver was still proprietary, but I stuck with them to support their efforts with my wallet. I’m glad I did because it’s been well over a decade since I had any GPU issues, and I no longer stress about whether the hardware I buy is going to work or not (so long as the Kernel is up to date).
If they’re going to release things under a proprietary license and send lawyers after individuals just trying to get their hardware to work, then yes, yes I can.
Don’t want to support it anymore? Fine. Open source it and let the community take over.
Assuming a full-time employer engineer works 20 days a month, that’s 50,000 lines of code a day.
Assuming an 8 hour work day, that’s 6,250 lines of code per hour, or 104 lines of code per minute.
This is humanly impossible without using AI and automation at every stage of the process. Good luck with that.
I’m guessing where we’re headed is software “engineers” becoming AI prompt “engineers” for design, development, review, testing, and shipping.
Buckle up, shit’s gonna get wild.
This is generally how new open source projects are born. Someone can’t find what they’re looking for among the current offerings so they make their own, fulfilling what they perceive to be a niche use case. Once they release it, it takes on a life of its own because it turns out it wasn’t a niche use case after all. Much to the horror of the dev, who now finds themselves the leader of an open source project.
Its a story as old as time.