It's complete crap, on the level of not being able to run the stopwatch in the background and having it restart if you get a notification.
Also, it's 65EUR if you want to order it in Europe
It's complete crap, on the level of not being able to run the stopwatch in the background and having it restart if you get a notification.
Also, it's 65EUR if you want to order it in Europe
Idk what's up with your fingerprint rant, but the drivers for that have been out for years. Not official ofc, but it works better than in windows.
The issue is that it's essentially useless because Linux has no support for any type of fingerprint reader, so you can maybe set up your DM to log you in.
Xkill doesn't kill the process, it just stops showing it to you
73 and 76, but I got them mixed up, ed is older.
That's for original Emacs though, the gnu version came out in 85
Emacs is older than ed
Sure, and not every arch user ends their comments with btw.
But that was consistent across multiple years, devices, and derivatives. It's usually a 5 min fix/workaround, but it's still annoying.
Nobody's raving about the install, that's just useful for people who don't know what makes a Linux distro.
It becomes your personality after a few years because every update might break anything, and you need to regularly maintain random shit. Also if you forget to update regularly, the chance of everything crapping out rises exponentially.
I hope you're using something like btrfs, because rollbacks are a must.
Does your company have a serious IT department that manage devices?
If yes, then you'll need to do whatever they say, and be ready to be told that's not happening.
If not, I'd suggest a stable distro, encrypt the disk, and use flatpak/nix to install fresh packages. Fedora could work, but I've had bad luck with it, and wouldn't want to risk my device crapping out because of an update.
The rest is really going to depend on your work and your it department.
Separate your system and user lists. Use home-manager for example for your user packages. I think separating those configs is the official recommendation.
As for the rest, I'm using nix on MX because of declarative package management. Screw going back to imperative and having to remember what packages to install. If it's something I use often it goes on a list, if I don't nix shell comes to the rescue.
I'd rather mess around with dev envs for nix than distrobox.
Damn you broke my brain for a second there. I thought you meant that nixos replaced k8s, and was wondering what the hell are you talking about.
If you're a developer and you don't know how to deploy to Linux servers you're useless.
Welp, found your red flag
I call bs or it was before they started shipping from EU. You literally couldn't order to Europe or EU countries from the other warehouse while they were stocking it.
It's got a lot more issues than that. It's utter trash unless you like want to practice CPP.