And from what I can tell based on the callout at the end… This is a line from connector which is a compatibility layer that allows running Fabric mods on Neoforge.

Which means connector is going to be included in every stack trace, regardless of how related it is to the problem. It will be the one to raise the errors that couldn’t be caught and managed… But AI will see connector being the one probably flagging the errors and be more likely to tag it as a “suspected” mod. I wouldn’t be shocked to find out that AI has a tendency to shoot the messenger.

“I tried to keylog myself and the system doesn’t support keylogging.” is a frustrating situation. Because it’s neat from a security perspective and absolutely maddening from basically every other one.

RIP stack overflow

https://www.youtube.com/watch?v=gmRk9Undc6U

You do know that you don’t have to change distros to change DE right?

Imagine having a router with an AP built in. We don’t use that consumer tier stuff around here. 😎

If someone else is getting paid the most amount of money, I’m happy to let the most amount of work fall to them. “Sharing the responsibility” doesn’t make sense if I don’t get to share the reward. It’s a company, not a community or a family.

You don’t have to have been a slave to have dealt with racism. Enough people still get really excited about their confederate flags that clearly the era is still heavily topical.

The word “confederate” means nothing beyond referring to a type of government, but when I hear it, I think immediately of the American civil war. Even though that ended in 1865 so I was never alive to witness that.

That’s not how word associations work.

Yeah. theres a fine line between advocating for positive change because it’s the right thing to do vs because it makes you look good. Theres a fine line between being an ally and empty virtue signalling, and those things may not look different within the scope of a single interaction. It can sometimes take a bit to understand if someone is genuine or just performing.

The point of political correctness is that it’s always things you’d never consider… but someone else does. I’m not here to say whether things are right or wrong or if “master” is good or bad. but you perfectly highlight the reasoning behind it.

To you, the only thing that comes up is the technology context. And that’s perfectly reasonable. To someone else, the unrelated slave owning context may just be tightly coupled with that word, and that immediately comes to mind when they hear the word regardless of context. And someone in that scenario is probably not having a positive correlation with the word.

So a group of people have a very understandable reason to have a negative correlation with the word, and it’s super easy to use a different word, so it seems to make sense to just use the other word.

All my git scripts these days have a $(git remote show origin | sed -n '/HEAD branch/s/.*: //p') in them, which just fetches whatever origin calls the head branch. so if I want to rebase from main/master/prod/lead/front/etc … the command will figure out which one to use for me.

I’m going to count vim, or any other IDE as a tool. You don’t just will your thoughts into the computer (at least most people don’t, that I know).

https://www.commitstrip.com/en/2017/02/28/definitely-not-lazy/

Right. 1F = 1C/1V … they could have just as easily said 1kF = 1C/1V. Many things use kg instead of g. You can tie together things other than the unscaled base units. Then they are still tied together but 1F is a more reasonable amount.

We just don’t make tech for old people the way we should.

My mother in law says things like “Wow, your son is just so good with computers.” She was impressed at how “tech savvy” he was because he was able to change the brightness on her phone for her so she could show him a picture better.

A lot of our UIs are built for absolute no-thinking usability. How would you propose changing the brightness on a phone that would make it more “old people friendly”. It’s not a matter of difficulty. She just doesnt remember these things, and a different flow may not necessarily be remembered either.

And I’m not saying its her fault or that she’s bad because of it. She was raised learning how to do and remember things a certain way and that has necessarily changed over the years.

A phone can do a lot of things, so unless you want to have 100 apps on your home screen, you’ll have to group some together. For instance, putting WiFi into a Settings app. Having every individual setting just available on the home screen potentially complicates things even worse by being overwhelming.

Genuinely curious how you think things like this could be redesigned to be more old people friendly.

According to Debian users, “stable” means “unchanging” and not “doesn’t crash or have bugs” … If you still ship 100% of the changes but just delay them by 2 weeks, you have the same number of changes. So by the Debian definition of “stable”, no, it is the exact same as arch.

By the everyone else definition where “stable” means “doesn’t crash or have bugs”, then also no. Shipping buggy code 2 weeks later doesn’t reduce bugs. And if you use the AUR at all, then things get worse, I’ve found, as the AUR pkgbuilds expect dependencies to match current up to date Arch repos.

tl;dr - no

Nano… Like… The one that has all the keybinds permanently shown at the bottom of the screen?

My arch install is 10 years old at this point.

I would be interested to know what inspired the need to “feel fresh” from OP. Is this an extremely underpowered laptop that just can’t handle having a few extra packages installed? Is it the Windows bad habit just making them perceive it as “needing a cleanup” ?

If you have hard drive space, unloaded packages are generally never loaded and just take up storage, not CPU/memory (though you should check to see what services are running too).

Also importantly. pacman -Qdtq and pacman -Rns are 2 separate commands. “Qdtq” means “Query, dependencies, unrequired, quiet” (“quiet” makes it so just the package names are output, to be more neatly piped into the second command. This queries the unrequired dependencies (ie, packages that were installed along with another package, but are no longer used by another package), and lists them “Rns” means “Remove, no backup, recursively” . and the - at the end means “Use the values from the first half of the pipe”… This removes the packages listed, skips creating any .pacsave fields for config files, and then once the package is removed, checks all of ITS dependencies to see if they can be removed as well.

For this command, a “dependency” is any package that is installed as a dependency of another package (and hasn’t been directly installed manually). If you installed package X, and it brought in package Y and package Z, then uninstalled package X, and now youre worried about package Y and Z, this will find them and clear them out.

This also teaches us that if you uninstalled package X with pacman -Rs packageX , the s bit would make sure that package Y and Z were cleaned up at removal time in the first place.

But overall, there’s very little reason to reinstall arch unless you are running out of disk space due to how many obsolete packages you have hanging around and they are all explicitly installed so wont be cleaned up with the above method.

But worst case, if you manage to break things just by clearing out unused dependencies, you can just copy your files off and do a full reinstall. Your system works right now, why reinstall? Might as well try to improve it a little bit (if thats even needed) before giving up and starting over.

“This hardware works fine and even has compatible software that it works great with. But I’m going to prefer the broken software for other reasons. And that means it’s the hardware’s fault.”

Software that is built to be compatible with a wide variety of hardware should be compatible with a wide variety of hardware.

If software can’t handle a 16.5:16 aspect ratio, then that’s bad software. I don’t care how weird of a niche thing that is… just make your software abstract enough to handle those cases.

It’s 2024, any resolution/aspect ratio/DPI combo should be supportable. There’s enough variety of monitors out there that we should have a solution for handling things on the fly without needing to have a predefined solution.

Indeed. “Linux” now means “literally Linux, the kernel” and also “an operating system that uses Linux as the kernel”. Kind of like how people say they use “Windows” but they mean that they use “Windows 11”.

The only reason saying “GNU/Linux” helps is if you want to give credit to GNU. It doesn’t add clarity to anything. Which is warranted, but also, what if I forked GNU and relabeled it as linux-tools. I believe that’s within my right, isn’t it? To fork and copy things.

It’s kinda odd to be like “copyright is bad, the works should be free, and just pass around naturally!” … “but also make sure I get credit”