Well, systemd developers made one of the classic blunders a software developer can do: make a program that has to deal with time and dates. Every time I have to deal with timestamps I’m like “oh shit, here we go again”.
Anyway, as I understood it the reason this is in systemd is because they wanted to replace cron, and it’s fine by me because cron has it’s own brain-hurt. (The cron syntax is something that always makes me squint real hard for a while.)
Free Software is Leftism because it has got us great software and maybe the only bad thing I can say is that release schedules aren’t a thing
Open Source is Capitalist Friendly because, ummmmm, extremely shitty Community Editions and putting everything cool in proprietary side, uhhhhh, random license changes to shit that isn’t actually OSD compliant, unghhhhhh, need of constant vigilance against license violations.
Like I am happy cheap hardware vendors have adopted OSS components but why are they frequently so shitty about everything
Hey, comparing Debian to a snail and its shell is unfair.
It’s more like a turtle and its shell.
Turtles can actually be surprisingly fast sometimes!
Plot twist: the “wolves” are just furries going to a major infosec conference, and will also talk endlessly about Linux
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?
I’m suddenly having flashbacks of the whole SCO fiasco. And people older than me probably have flashbacks of the BSD/System V lawsuit.
I mean, this thing is fun to argue about, until you remember people used to argue about this in court.
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.”
Actually this reminds me, what is the deal with tar command recommendations to use or not use dash? I know GNU tar accepts both (e.g.) tar xvf file.tar and tar -xvf file.tar, but at some points people were like “NO! Don’t use the dash! It’s going to maybe cause issues somewhere, who knows!” and I was like “OK”. Something to do with people up designing the Unix specs?
About 10 years ago I was like “FINE, clearly 512MB of memory isn’t enough to avoid swapping hell, I’ll get 1 GB of extra memory.” …and that was that!
These days I’m like “4 GB on a single board computer? Oh that’s fine. You may need that much to run a browser. And who’s going to run a browser regularly on a SBC? …oh I’ve done it a lot of times and it’s… fine.”
The thing I learned is that you can run a whole bunch of SHIT HOT server software on a system with less than a gigabyte of memory. The moment you run a web browser? FUCK ALL THAT.
And that’s basically what I found out long ago. I had a laptop that had like 32 megs of memory. Could be a perfectly productive person with that. Emacs. Darcs. SSH over a weird USB Wi-Fi dongle. But running a web browser? Can’t do Firefox. Opera kinda worked. Wouldn’t work nowadays, no. But Emacs probably still would.
Windows devs: “We need to ask the keyboard makers to add a special key for OS stuff. A Windows key. Yeah.”
KDE devs: “There’s something special about the K key, and none of us can put it to words.”
deleted by creator
Yeah, I just tried upgrading my Gitea Windows instance to Forgejo via Docker, and it actually works pretty much as easily as it did before. Fantastic! Might just leave it here instead of shoving it all in the VM - I can always do that later if it’s necessary. Having a full VM does have upsides, but in this particular instance this is definitely good enough.
Well cron is “really easy” as long as your requirements are really easy too.
Run a task at specific hour or minute or weekday or whatever? Easy peasy.
Run a task at complex intervals? What the fuck is this syntax. How do I get it right even. Guess I’ll come back next week and see if it ran correctly.
Actually have to look at the calendar to schedule this stuff? Oh lawd here come the hacks, they’re so wide, they’re coming
Run a task at, say, granularity of seconds? Of course it’s not supported, who would ever need that, if you really need that just do an evil janky shellscript hack