> In software engineering, we learned a long time ago that giant monoliths are not the answer.
That depends on the question. If the question is "How do I utilize 10,000 software engineers?" then yes, a monolith is not the answer. However, this isn't a problem most companies face. Starting out with microservices is rarely a good idea either as you'll have a hard time getting the boundaries right.
Honest question, is it worth it for an average user to file reports?
The first time I tried this was the last time I tried. It was ca. 2012 on an Acer laptop that I personally configured to dual-boot. My memory is not to be trusted but
- the biggest problem for me was that it asked for a core dump/logfile, which I agreed to, but for some reason or another it could not produce/extract said debug info and I got stuck in a loop of whoopsie trying and failing.
- smaller grievance (I might be wrong) is that I had to create some account (Launchpad?) in order to report the bug. Why can't it be anonymous?!
Everytime I turned this Acer laptop on, there will be 2-3 such prompts from Ubuntu that something report-worthy went wrong. You learn to blend it out like the cookie consent dialogs but still annoying. Plus, everything is still perfectly usable so it does seem like the OS is just making a mountain out of a molehill.
In my experience every time I go to report a bug or submit a feature request on anything, I find that someone else has already done so it and a maintainer has responded with one of these:
Look dude, let's get something straight: just because someone didn't jump on command for that one patch you suddenly care about out of the blue, doesn't mean they're LARPing on anything.
If you want to dismiss other people's work like that, have at least some decency to provide a track record beyond "they didn't do what I wanted REEEEEEE!!!!" type response.
my DO droplet was like 100 years old and I never tried once to update any software I had running on it or the OS, then said hmm that's probably bad. Now for most stuff other than password manager I had running on there, hack it, I don't even care. Not the password manager though, can't be risking that.
Got it. If you want to self-host again at some point you could add a VPN layer and configure unattended-upgrades with automatic reboots. With an Ubuntu Pro subscription (free for up to 5 personal devices) you can even get kernel live patching. Once that's taken care of you can automate the app updates with systemd timers / cronjobs and small scripts.
reply