We’re not. Jack is just another way to say “guy”, “man”, or “dude”
Edit: or more specifically but less relevant now, “peasant” or “commoner”, someone of low social status.
Kind of interesting to compare to “Guy”, another instance of a given name turned into a generic term.
That’s not really a hierarchy thing though.
Just a measure of how skilled / experienced someone is, and how suitable it is for them to be teaching someone else.
I think we need more people sharing their knowledge and we don’t need the blind leading the blind.
I’ll add the PineTime to that. Doesn’t do anything too fancy but it works well enough.
If it helps, there is evidence that you don’t actually need to reference them. Just writing them down helps the memory process.
https://www.scientificamerican.com/article/why-writing-by-hand-is-better-for-memory-and-learning/
It’s the software [developer]’s fault that it doesn’t do its job properly.
Hopefully you don’t find occasion to read about Hafþór Björnsson too often.
I understand it. Who wants to use two passwords to access their computer?
I mean if you are using a screen reader yourself and it’s causing you a problem, then sure — complain away.
Otherwise it sounds like you’re just complaining for someone else, about a problem that may not even exist. “Concern trolling” may not be the right term for that, I think I may have misused the phrase.
But: do screen readers actually have difficulty with the letter thorn? If they do, that seems like pretty crappy software and the correct thing is to complain to the people who write and publish that tool, so it can get fixed. Not tell everyone to limit their text to ascii.
Sounds like they need better screen readers. And are you affected or just concern trolling?
DNF (abbreviation for Dandified YUM)
These guys at Redhat don’t know how abbreviations work, I guess.
The logic is that the most useful app will be the most popular by virtue of its utility.
Not always true but I’m sure there’s some correlation.
Tenacity is the only one that is still actively being maintained.
I’m glad they stuck with it!
The video is great, and I’m excited for the new Audacity. But that logo/icon is an abomination.
Fond memories yes. It taught me so much about how the build process works and how the underpinnings of Linux worked.
I was afraid of that. Glad you figured it out! Maybe I should’ve quoted it…
Fond memories of Linux From Scratch, here.
It seems only natural…
Anecdotal example: just yesterday I found out that I broke my file picker function in five out of six web browsers, by loading an Xcompose file with some definitions that GTK apparently doesn’t like. It took me about 5 hours of poking at things to figure out that a change I did a week ago, broke a function I hardly ever use. So I did fix it eventually but I it took me a week to notice and then hours to track down what was going on.
Is there any chance at all that the casual users would be using a compose key, let alone loading a custom definition file for it? Hell no!
But here’s the secret: there is nobody out there who is the perfect expert who never makes a mistake and knows all things. We’re all out here pushing boundaries; the only difference is where those boundaries are.
This applies outside of IT just as much, maybe more. It’s the rare person who will admit it though.
Kinda yeah, but I think that just comes from storing the output of the PWD command.
The system call that returns that value is called getcwd().
Kinda, but it’s pretty much all horrendously outdated bitching about superficial flaws in tools from 40 years ago.
… 9/10 response. I chuckled!