she/they
- 0 Posts
- 17 Comments
2·5 days agoIt’s been a while since I last gave it a try, but I remember frequently ending up in strange states where a window wouldn’t want to tile properly. Windows would also frequently end up overlapping or extending beyond the screen, in ways they just wouldn’t when I was using Sway, Hyperland or Niri. IIRC mouse dragging and mouse resizing windows was extremely jank too.
Most of this is KWin’s fault as far as I know, it’s built for stacking window management and there’s only so much you can fix with scripting around it. It’s also the reason for the bad multi-monitor experience; the way it interacts with workspaces in particular is in my opinion not useful and never what I want.
Additional cons:
- Layouts break easily
- Multi-monitor is close to unusable
Extensions aren’t apps. Imagine all mods would break if a game is updated and you’d have to wait… oh yeah you do, because that’s how these things work.
You’re welcome, glad I could help :)
FN keys are usually handled at a firmware, sometimes BIOS or driver level. This makes them completely inaccessible to keyboard remappers (they have no idea when it is pressed), which is why none of them can do this.
This Stackexchange answer looks like it should contain the information you need, but I don’t have a 2014 MacBook to test it.
You could make the same kind of articles for the old coreutils if you really wanted to. Just creatively “rewording” the bugfixes from the recent 9.8 release:
- GNU Core Utilities Are Causing Failures [when copying between NFS and non-NFS filesystems with ACLs]
- GNU Core Utilities May Cause Data Corruption [with copy ranges larger than 2 GiB]
- Correctness Bugs Found in GNU Core Utilities [
tail --pidmay race with reused PIDs]
I feel like the reactions regarding
uutilsare a bit… off in general. There seem to be a lot of people who are pathologically negative towards open source projects for, frankly, bullshit reasons, like vague complaints about “Rust evangelism” (what?) or how permissive licensing is against the spirit of open source (WTF).Phoronix isn’t helping with these clickbait articles which border on content farming and their failure to moderate their comments of course, but these negative attitudes seems to cut across sites, also including Lemmy, Reddit and even Hackernews.
The
uutilsteam seems to be doing well but it makes me sad to think about any aspiring open source devs without corporate backing reading such drivel.
You could always swap out crons, syslog, init systems, and it would not affect Gnome.
That just isn’t true. Both GNOME and KDE already have hard dependencies on systemd-logind. GNOME hasn’t supported non-systemd Unixes since 2015! The only reason it works is that the elogind project provides a systemd-logind implementation decoupled from the rest of systemd. The GNOME team has elected to give users of elogind (despite not being officially supported) advance warning that they’ll have to do some amount of extra work in the future if they want to ship GNOME 50. Honestly I think that’s quite fair of them.
There are more GNOME features that don’t work without systemd even if it launches, like application isolation using systemd scopes. Fundamentally this is about not having to reinvent the world. Why should every DE have bespoke implementations of user, login and service managers instead of just using the ones that 99% of user systems already have?
7·1 month agoI can’t speak for everyday workflow (having discovered this project less than a week ago), but rebase being unnecessary and cherry-pick not creating duplicate commits seem like the most notable advantages to me.
Nu’s
findbuiltin isn’t a GNUfindrepacement. I think what you actually want islspiped intowhere:ls **/* | where type == fileI do question the choice to alias a well-known program with a builtin that does something entirely different. You can also use
^findto avoid calling the builtin. I would’ve expected\find(bash-like) orcommand find(fish-like) to work as well, but alas…
That’s not entirely true, unless you choose to nixify everything. You can just have a basic Nix configuration that installs whatever programs you need, then use stow (or whatever symlink manager you prefer) to manage the rest of your config.
You can’t entirely forget that you’re on NixOS because of FHS noncompliance but even then getting
nix-ldto work doesn’t require a lot of effort.
No C program is written to satisfy a borrow checker and most wouldn’t compile with one, so adding it would require rewriting the world anyways. At that point why not choose a language that, in addition to being memory safe, also drastically cuts down on other kinds of UB, has sum types, sane error handling, a (mostly) thread safe standard library, etc.?
The mentioned performance governor runs the CPU permanently at maximum frequency, which is obviously bad on battery powered devices and on devices with lacking thermal headroom. I think it might cause problems in virtualized environments as well but I’m not sure about that.
To be fair showing the overview on startup makes perfect sense on vanilla gnome, it’s only dumb if you install one of the two specific extensions that partly replace it.
Running
poweroffis one of the correct ways on anything Systemd (details). If that doesn’t work then something is broken.If you haven’t done so already try looking into the journal.
sudo journalctl -b -1 -ewill take you to the end of the log for the last boot.
23·7 months agoI am very sorry to remind everyone about the existence of Visual Basic, but it has:
- VbCrLf
- VbNewLine
- ControlChars.CrLf
- ControlChars.NewLine
- Environment.NewLine
- Chr(13) & Chr(10)
And I know what you’re asking: Yes, of course all of them have subtly different behavior, and some of them only work in VB.NET and not in classic VB or VBA.
The only thing you can rely on is that “\r\n” doesn’t work.
GUIs do have advantages in things like discoverability. Honestly the 1983s Apple Lisa nailed this with the idea of having clickable menus annotated with keyboard shortcuts, so users could do the same thing faster next time. For some reason we stopped doing this (especially in web apps), but that’s a reason to make better GUIs, not to RETVRN to the feature set of a VT100.
I don’t know why we have to go on nonsensical diatribes about “UNIX wizards” though when we’re fundamentally talking about a handful of minor UI improvements to things that already exist.
Yeah that’s not going to work in the general case. An trivial RPM package might be fine but every additional dependency increases the chance that it depends on some package that OpenSUSE doesn’t know. There’s a reason OpenSUSE is usually considered an independent distro and not a “Fedora-based” one despite some shared components.
I don’t think security wise there’s much of a difference between running random software directly or via distrobox. Note that distrobox mounts your entire home directory into its containers, which removes any security benefit that containers could theoretically bring. In either case you either need to audit the software yourself or you need to trust whoever you’re downloading the software from.
Out of the third party repositories you mentioned, I would personally consider Nixpkgs the most trustworthy because package specs are actually code reviewed, unlike the AUR into which anyone can publish packages with zero oversight. That doesn’t mean it’s impossible for Nixpkgs to end up with malware in it, but the AUR sets a low bar. Using Nix (not NixOS) is also not actually that hard, you can just run
nix-env -iA nixpkgs.yaziand it does exactly what you would expect, even if NixOS users would scoff at the “imperativity”.That being said, the OpenSUSE repositories really aren’t that bad. Especially if you combine them with Flatpak, and especially if you install Firefox and VLC (or equivalents of your choice) from Flatpak so you don’t need proprietary codecs in your base system. I used OpenSUSE Tumbleweed for years and got by just fine without Nix, homebrew or distrobox.