Last year, money was running out in our project and the guy who had trained me decided he’d take the L and move to another project, so we could continue in the project. And yeah, suddenly I was in the role of the lead developer.

Like, don’t get me wrong, I would’ve been the one to be moved to another project, if I wasn’t up for the task. It’s not like I was a complete dumbass.
But it did still feel more like “I guess, we doin’ lead development now” rather than something I had intentionally worked towards.

I mean, depends on the country. Labor laws here in Germany mean that it’s worth investing into workers and when you have invested, it costs you significantly more when they quit than if you just paid them reasonably.

Title a dialog “Your ads, your choice” and then don’t give a choice to say no. You’d think their marketing department would realize how awful this looks…

I can’t really sell this as a solution, as it requires quite a lot more involvement than a simple configuration file should, but I use Nix Home Manager with Plasma Manager for this.

This is part of the tooling you’d use on NixOS, but you can use it on other distros, too, and it generally works fine (although I’m not sure, if the current version of Plasma Manager still supports Plasma 5, in case you’re still on a distro with that).

Basically, it allows you to define e.g. keyboard shortcuts like this:

    shortcuts = {
      ksmserver = {
        "Lock Session" = [
          "Screensaver"
          "Meta+Ctrl+Alt+L"
        ];
      };

      kwin = {
        "Expose" = "Meta+,";
        "Switch Window Down" = "Meta+J";
        "Switch Window Left" = "Meta+H";
        "Switch Window Right" = "Meta+L";
        "Switch Window Up" = "Meta+K";
      };
    };

It then fucks up the formatting, so that it looks like KDE expects, and throws it into ~/.config/kglobalshortcutsrc.
(KDE does actually have a text-based config, it’s just borderline unusable.)

Well, and you can do this with lots of other Plasma options, too. Here’s their official example: https://github.com/nix-community/plasma-manager/blob/trunk/examples/home.nix

Yeah, HeliBoard or FlorisBoard would’ve been my recommendation. They’re very similar, though (and presumably share most code between themselves).

Multiple people have said that, yeah. But they also said that he did not particularly distance himself from the project, which is definitely something I would do, if I found out about this kind of backing.

Believe what you want, but Drew DeVault has more of a reputation than FUTO.

From a communication viewpoint, that is fair, but to my knowledge (from being a professional software developer), effectively any license that is not ‘open-source’ or ‘free’ is by definition proprietary.

Because those two terms describe licensing standards (the only established ones that I know of). Whereas I believe, “proprietary license” uses this meaning of proprietary:

Nonstandard and controlled by one particular organization.

So, they wrote that license themselves is the point. What it says in there is secondary in meaning.

This is so highly relevant because in legal disputes, there is certain license compatibilities which are known to be possible.
You can take a library licensed under the MIT license and use it in a project that uses the Apache-2.0 license and you’re perfectly fine. This is the foundation of why the open-source ecosystem exists at all.

But you cannot take the source code from FUTO and use it in a differently licensed project, because no legal precedents exist to support this. (I believe, the FUTO license also actively prohibits this in some way, but that’s beside the point.)
This has massive implications. Like, yeah, you can look at the code, but it is useless. If FUTO closes shop or enshittifies, you cannot fork their projects.
And because you cannot legally re-use their source code in other projects, likely no one looks at it in depth either.

Here they started doing such phishing tests a while ago and our IT department had significantly worse stats than other departments, in terms of how often we would click on the link in the phishing mail.

And yeah, the conclusion was that we were just being asshats that decided to poke around in the obvious phishing mails for the fun of it. Rather than getting extra security training, management told us to just stop dicking around, so that our stats look better.

Damn, I’ve had technological disagreements with Mr. DeVault in the past. Obviously, I did not assume those to mean I’d disagree with him on everything, but it still feels surreal to read an entire post where I’m fully on board with everything he writes (and appreciate all the info I did not know).

Cool to see that he’s fighting the good fight.

Yeah, that’s so ridiculous. They could’ve just turned off the heating and made it lay flat, and it would’ve been fine. But evidently, they did not even think about handling an outage.

I find that if your command is complex enough that editing it on the terminal becomes annoying, then there’s a very high chance you want it in a file anyways, just to document what you did and to allow easily re-running it.

Having said that, you can also have your shell open the command in your editor of choice: https://www.stefanjudis.com/today-i-learned/edit-long-shell-commands-in-your-usdeditor/

I’m not super deep into Flatpak, but is there such a thing as a “distro’s Flatpaks”? Normally, it uses central repositories like FlatHub, which are intentionally distro-independent.
A distro-specific repository would only make sense, if your distro maintainers are developing custom tooling…

I’d argue that it’s Android’s DE for Linux.

Works fine for me. ¯\_( ᵔ ~ ᵔ )_/¯

A colleague always complains that KDE looks like Windows. She does also get jealous, though, when she sees me using poweruser features.

It’s like flying on a broom. Perfectly logical.

Damn, I hadn’t seen the community name before reading the title and thought Microsoft was fixing up their filesystem. Of course, there’s more development happening on the non-Microsoft side.

It also doesn’t just look like a tiling WM. OP is using Krohnkite, which actually gives KDE tiling window management.

There’s no way they actually checked that it works. It includes code for:

• XDG
• GNOME
• “GNOME_old”
• KDE

Verifying this would mean logging into several different desktop environments.

It’s also extremely fragile code, running external commands and filtering through various files. There just is no good API on Linux for querying whether the desktop environment is using a dark theme, so it’s doing absolutely inane shit that no sane developer would type out.

Because it’s a maintenance nightmare. Because they almost certainly don’t actually need to solve this. That’s software development 101, to not write code that you don’t actually need. But apparently some devs never got the memo that this is because of the maintenance cost, not because you weren’t able to generate the code up until now.