• 1 Post
  • 64 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • Of course, if you’re living in Russia, it’s dangerous to state anything other than support for Russia’s invasion of Ukraine.

    That doesn’t mean it isn’t cringeworthy to watch someone awkwardly dance around it, trying to ignore it while complaining about (checks notes) losing a bit of reputation over an unnecessary war that their country started and which literally cost thousands of lives.

    Any Russian who stands up against that is incredibly brave. The others, just different levels of sad. Non-Russians who support Putin are the worst.

    I understand why you’d want FOSS to not care abot borders, wars and politics and that is noble. But to call this comment racism, comes across as a veiled show of support for Putin. As if critiquing his invasion is a racist act that hurts the Russian people. Putins invasion is hurting the Russian people. Not this comment.





  • Yes, you are right.

    The old stuff, now no longer supported, is:

    • .NET Framework up to and incl version 4.8
    • Runtimes distributed as part of Windows
    • Mono is a Linux Runtime used for compatibility

    The new stuff:

    • .NET Core, up to and incl 3, more recent versions are named .NET from version 5 onwards (to prevent mixing it up with the old Framework)
    • Is completely cross-platform, natively
    • I don’t know about desktop specific graphical stuff but that probably depends



  • 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 ties 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 mot 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 by those old versions.








  • 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 codecbIbcouls 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…


  • Exactly! If you only have to edit small text files on a server once in a blue moon, nano is much less biomemory-heavy. But if you regularly write docs and code in l vim or neovim, it starts to pay off after a week or two.

    I really enjoyed learning to quickly select and change entire words or lines, doing things like: :%s/replace_this_text/with_that/g Etc. If you enjoy that, you will soon get to a point where you miss the motions in your regular editor and install a vim extension in VS Code and stuff, just before fully switching to neovim