MacOS

I had a go at using guix as a package manager on top of an existing distro (first an immutable fedora, which went terribly, then OpenSUSE). Gave up for a few reasons:

• As mentioned in the article, guix pull is sloow.
• Packages were very out of date, even Emacs. If I understand correctly, 30.1 was only added last month, despite having been available since February. I get that this isn’t the longest wait, but for the piece of software you can expect most guix users to be running, it doesn’t bode well.
• The project I was interested in trying out (Gypsum) had a completely broken manifest. Seems like it worked on the dev’s machine though, which made me concerned about how well guix profiles actually isolate Dev environments. This was probably an error on the dev’s part, but I’d argue such errors should be hard to make by design.

All in all I love the idea of guix, but I think it needs a bigger community behind it. Of course I’m part of the problem by walking away, but 🤷

Keep the files in a dedicated torrents folder then make symlinks to where you actually want them?

Be aware there are basically two different things called Owncloud. There’s still the original php version, which is similar to nextcloud but worse (not open source, smaller plugin ecosystem I think)

On the other hand is owncloud “infinite scale” (or ocis). This is the thing entirely written in go. But as others have pointed out, it’s little more than a file server at this point.

IMO the self-hosting community is really missing a self-contained “all the DAVs” server (files, calendar, contacts). Baikal etc seem like a great start, but it would be great to have somewhere to get those parts pre-assembled. Until then, nextcloud works for me.

Are there any new features in particular you’re hoping for?

For me, those two are the only things I can remember thinking it would be nice to have. Q

Sounds minor, but I’m excited for right aligned mode-line segments. I’ve been working on a minimal powerline-esque theme and this will make it soo much cleaner.

To be honest, I find my Emacs config important enough to live at the top level of my home directory.

Plus we could also get rid of the hacky risky vs safe dir-locals system that fills up custom.el with clutter

To add some more context:

Eglot is part of Emacs now, so it comes preinstalled. It’s good at finding lsp servers, but won’t help you to install them. Definitely the option if you want to keep things simple and can live with the need to manually install servers. (Also a quick note, the hook you should use to auto activate eglot is eglot-ensure, rather than just eglot.

I can’t imagine that’s any more free than bitwarden?

Obviously there’s a lot of caveats about how representative this survey (or any other survey) is of the broader population, but I think this is a good reminder of how weird we all are. Nobody on here claims to use Ubuntu or Manjaro, yet they are more popular than Fedora (and potentially even arch, when steam decks are discounted).

There’s nothing wrong with that, I love the weirdness of the Lemmy Linux community! I just always think it’s good to appreciate when opinions (like my love of ublue) aren’t as popular as you think they are.

Please somebody correct me if I’m wrong, but I really don’t find the “chip makers don’t have to pay licence fees” a compelling argument that RISC-V is good for the consumer. Theres only a few foundries capable of making CPUs, and the desktop market seems incredibly hard to break into.

I imagine it’s likely that the cost of ISA licencing isn’t what’s holding back competition in the CPU space, but rather its a good old fashioned duopoly combined with a generally high cost of entry.

Of course, more options is better IMO, and the Linux community’s focus on FOSS should make hopping architectures much easier than on Windows or MacOS. But I’d be surprised if we see a laptop/desktop CPU based on RISC-V competing with current options anytime soon.

I feel this. I remember spending ages trying to figure out how to remove the bar in doom modeline (yes eventually I realised I could just make it the same colour as the background…), only to discover that it was necessary to control the size of the modeline.

I imagine this stuff is really deep in the internals of Emacs, which is why people are less keen to touch it. But if we were in the mood to do that, I would like even more CSS-like features, such as the ability to configure each side of a box property independently

In my experience it Just Works ™️. I spin up a distro/toolbox, compile some software (e.g. Emacs) then run the executable inside the container, and up pops the GUI window.

If you use distrobox, you can even distrobox-export desktop files, at which point a containerised gui application is practically indistinguishable from one installed on the host system

Its all about how an application goes from “I would like to display X on a screen” to how X actually gets displayed. Wayland is effectively a language (technically a protocol) that graphical applications can speak to describe how they would like to be drawn. It’s then up to a different program more deeply embedded in your OS to listen to and act on those instructions (this program is called a Wayland compositor). There’s a lot more to it (handling keyboard input monitor settings, etc), but that’s the general idea.

Wayland is a (relatively) new way of thinking about this process, that tries to take into account the wide variety of input and output devices that exist today, and also tries to mitigate some of the security risks that were inherent to previous approaches (before Wayland, it was very easy for one application to “look at” what was being displayed in a completely different app, or even to listen to what keys were being typed even when the app isn’t focussed).

Thing is, change is hard, doubly so in the consensus driven world of Linux/FOSS. So, until the last couple of years or so, adoption of Wayland was quite slow. Now we’re at the point where most things work at least as well in Wayland, but there’s still odd bits of software that either haven’t been ported, or that still rely on some features that don’t exist in Wayland, often because of the aforementioned security risks.

Kotlin targets the JVM right? I think you’d need either a port of the runtime (dalvik?) Or an api translation later a la WINE.

But I don’t actually know anything, so don’t listen to me. Having a fully Foss phone with support for the android app ecosystem would be wonderful though

By default, XWayland apps are now allowed to listen for non-alphanumeric keypresses, and shortcuts using modifier keys. This lets any global shortcut features they may have work with no user intervention required, while still not allowing arbitrary listening for alphanumeric keypresses which could potentially be used maliciously

This is… very smart actually. Any reason this is limited to Xwayland? (Is that XDG portal a thing yet?)

I do wonder what percentage of Linux users reject the survey compared to Windows users. Not that it’s changed much, but every little helps right?

Eventually valve will probably push a SteamOS update out with plasma 6. But it’ll be up to then when to do it.

Whilst I agree that that’s a nice option to have (more options are usually better!) I’ve come to love the linux way of distribution via repositories. These days I barely use the cli too: GNOME software and KDE’s Discover are great. Perhaps an official nightly flatpak would be best?