A "hbox" in TeX is a horizontal box. In 99% cases when laying out text, it's a line of text. "Underfull hbox" means "I couldn't stretch the content of this line far enough, so it will look janky as f due to the increased spacing". "Overfull hbox" means "Well, I tried my best to hyphenate and line-terminate, but this word will stick out of the margin and will look stupid as f."
Most of the time this is caused by a word that auto hyphenation can't deal with. You need to add a manual hyphenation exception. I can't remember how to do that, sorry, because it's been a while and also I'm mildly drunk, sorry.
Back in 1997 I was like "Ooh, Debian is mildly easy to install (compared to Slackware). Just need to engage my brain a few times maybe."
(The first Slackware guide I read in 1996 had an ominous warning about getting the ModeLines right in XFree86 or the monitor will catch fire. This, fortunately, was a little bit of exaggeration. Over/under refresh frequency protection was already a thing.)
Now? "Oh no I fucked up my password shit and can't login. I'll need 5 more minutes to completely reinstall this Raspberry Pi image. I should have engaged my brain!"
Shit, we've gotten to the point that your average desk jockey can probably install freaking FreeBSD on the first try. If that's not a good sign I don't know what is.
Not "auto trust", of course, but rather make adding keys is a bit smoother. As in "OK, there's this key on the web site with this weird short hex cookie. Enter this simple command to add the key. Make sure signature it spits out is the same on the web page. If it matches, hit Yes."
And maybe this could be baked somehow to the whole APT source adding process. "To add the source to APT, use apt-source-addinate https://deb.example.com/thingamabob.apt. Make sure the key displayed is 0x123456789ABC by Thingamabob Team with received key signature 0xCBA9876654321."
I'm a Debian fan, and even I think it's absolutely preferable that app developers publish a Flatpak over the mildly janky mess of adding a new APT source. (It used to be simple and beautiful, just stick a new file in APT sources. Now Debian insists we add the GPG keys manually. Like cavemen.)
Up to 2.x, GNOME used what was basically the MacOS philosophy: make things easy and simple and intuitive, but if the user wants finer control and power features, make sure it's still possible somehow. GNOME 3 and later pretty much adopted the philosophy that there's the GNOME path of simplicity and streamlining, and power user functionality is going to be removed from the core and relegated to extensions. And, of course, GNOME started requiring boatloads of memory to run, which to me didn't go hand in hand with "simplicity".
I eventually settled on using XFCE, because it didn't have the bloat and still had enough customisability. Really good environment for old and underperforming systems. If I'm using a modern high performance system, I'm actually pretty impressed by what KDE Plasma is doing these days.
GNOME 1 & 2: The dock is in the bottom by default. It can be moved elsewhere if the user prefers it.
GNOME 3+: The dock is wherever we think the user is likely to find it. Maybe it's in the bottom. Maybe it's nowhere. Maybe it's everywhere. Verily, who can even begin to understand the mysteries of the brain?
Debian's Firefox is Firefox ESR, or Extended Support Release. It's behind the bleeding edge, but gets security updates.
If you want the bleeding edge Firefox, you can add Mozilla's own APT repository and install it. Doesn't even conflict with Debian (firefox-esr vs firefox, it even uses a separate user profile by default). Instructions are on the Firefox download page somewhere.
When I was learning about GIMP key shortcuts I was like "Ctrl+A selects everything, Ctrl+Shift+A deselects everything. Makes sense."
And then I went to most of the other apps. "Ctrl+D? Well it's one less keypress, but... WHY?"
To be fair, I get it now, I've used plenty of image editors and I remember the keybinds wherever I am. Just that I sometimes find it annoying that The Other Software hasn't adopted logical keybindings.
(I find it particularly annoying that a lot of image editors try to be fancy and sophisticated and Photoshop-compatible and think it's at all appropriate to use Ctrl+NumpadPlus and Ctrl+NumpadMinus for zooming. Just use what GIMP uses! NumpadPlus and NumpadMinus. It's not hard! What are you using the plain plus and minus for, anyway? Absolutely nothing! I just checked, I need to use Ctrl in Affinity Photo. Plain plus and minus are useless. I see you. ...oh I can just rebind these. Done.)
I've been using GIMP since the very dawn, I use plenty of other image editors for variety of reasons (Affinity Photo, DxO PhotoLab, ArtRage, Clip Studio), and I have no problems with the UIs in any of them.
Yet every time I use Adobe software I'm like "why is it doing this? Why is it designed this way? Who thought that was a good idea? This is stupid."
Fun thing, the last time I used LimeWire was actually in Linux. So obviously I was immediately highly suspicious about .exe results. (Wouldn't even have been able to run them anyway. Wine was far less functional back then.)
For data gathering? Pretty much anything that doesn't fiddle with the values. Usually, bespoke apps or applications specifically designed for survey data. People actually use spreadsheet programs a lot, but those who do spend a lot of time on ensuring data gets entered correctly.
When I was taking my introductory courses in computer science over 20 years ago, they told me to not use Excel if you can avoid it, because it's not very, you know, precise. So I'm well aware that this is an ancient joke. Excel will fuck your data up - AI is just another way to do it.
But it is a potential scifi plot point.
However, I will concede that it's probably not a scifi plot point for too long. Worse things have already happened.
(furious scribbling in the scifi worldbuilding notes) "In 2050, the names of the months got inadvertently legally changed when a megacorporation released a new version of their office suite and silently corrupted thousands of government document drafts."