• 7 Posts
  • 98 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle




  • I have never heard of WattOS but that sounds terrible.

    It seems like antiX is a systemd-free Debian flavor.

    If you want systemd, why not just use Debian? Or, if you are looking for a nice preconfigured DE/WM, any of a number of Debian/Ubuntu derivatives.

    Mint for best out of the box setup, Pop!_OS for tiling, Zorin OS if you’re looking for a funky styling, any of the Ubuntu derivatives for the major DEs: Kubuntu, Xubuntu, etc.


  • Makes sense. Mono was necessary in the “old .NET” world, where runtimes were tied to Windows versions and the framework was a pure Windows framework. Mono made it possible to run old dotNET framework versions (up to 4.8) on other OSes.

    Since dotNET Core and then dotNET 5 and higher, the framework itself is cross-platform so Mono is not necessary anymore, except for backwards compatibility for apps that use a now unsupported framework.

    So it makes sense that Microsoft, after dropping the old dotNET Framework versions, also wants to stop supporting the cross-platform library that was only needed for those old versions.












  • F04118F@feddit.nltoLinux@lemmy.mlHow bad is Ubuntu?
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    1 month ago

    Completely off topic, but: I’ve been trying Fedora (KDE spin) for a few months now, and I’m flabbergasted at how unusable the distro version (not the Flatpak) of Firefox is. I think it’s a codec issue as I’ve checked Firefox is running in wayland mode, but:

    • video calls (Zoom, Slack) don’t work.
    • despite installing every codec I could find through Fedy, a package manager for non-free Fedora repos.

    Meanwhile, the Microsoft Edge flatpak works flawlessly.

    Are you using a flatpak browser too? If not, how did you get your browser to work?

    I really like Fedora otherwise: up-to-date kernel and modern (very efficiently stored) packages, but properly tested with major releases, btrfs and systemd by default and commonality with RHEL is useful at work.

    But these codec issues are pushing me back to Arch…




  • I um… didn’t get started yet. But a colleague demoed it to my and it’s kind of between virtual environments and containers, if you’re familiar with Python.

    You write a Nix config and specify exactly which versions of which package you want to have. Reproducibility is the main selling point of Nix. Things don’t just break overnight because a dependency of a dependency of a dependency got upgraded. You can always go back to exactly what it was like before. Guaranteed. That’s pretty cool.

    Ok so you got that config, then you build and activate it, and it replaces your shell. You enter the Nix shell. You still have access to all your files and directories, but your Nix config controls exactly which versions of your tools you have. gcc, npm, python, maven, whatever you use.

    You can see why this makes people want to build an immutable OS.

    The main drawback of Nix is that it has a bit of a learning curve. Hence why I haven’t started yet. Maybe it’s time though.