• 5 Posts
  • 28 Comments
Joined 2 months ago
cake
Cake day: April 2nd, 2025

help-circle
  • On Debian Bookworm with the non-free-firmware repo enabled…

    $ apt-cache pkgnames firmware | sort
    firmware-amd-graphics
    firmware-ath9k-htc
    firmware-atheros
    firmware-b43-installer
    firmware-b43legacy-installer
    firmware-bnx2
    firmware-bnx2x
    firmware-brcm80211
    firmware-cavium
    firmware-cirrus
    firmware-intel-graphics
    firmware-intel-misc
    firmware-intel-sound
    firmware-ipw2x00
    firmware-ivtv
    firmware-iwlwifi
    firmware-libertas
    firmware-linux
    firmware-linux-free
    firmware-linux-nonfree
    firmware-marvell-prestera
    firmware-mediatek
    firmware-microbit-micropython
    firmware-microbit-micropython-doc
    firmware-misc-nonfree
    firmware-myricom
    firmware-netronome
    firmware-netxen
    firmware-nvidia-graphics
    firmware-nvidia-gsp
    firmware-qcom-media
    firmware-qcom-soc
    firmware-qlogic
    firmware-realtek
    firmware-samsung
    firmware-siano
    firmware-ti-connectivity
    firmware-tomu
    







  • This is a huge win for the open source community!!

    The headline alone? No, I don’t think so, because AMD’s driver had a reputation for working in some situations (mostly non-gaming IIRC) where Mesa didn’t.

    However, this bit quoted from the release notes might make up for it:

    “The Mesa Vulkan driver will be officially supported, along with Mesa OpenGL and Multimedia support.”

    Assuming they mean that AMD will work with Mesa to get the remaining edge cases fixed, so that the proprietary driver is no longer needed at all, this does seem like good news.






  • Current web browser engines generally support JavaScript and WebAssembly, and no others (unless via a plugin, as with Java).

    So, if I understand you correctly, your options are to find a language that transpiles down to one of those two (several such languages exist), or find an engine that isn’t precisely a web engine but supports some alternative language(s). I don’t know any useful examples of the latter, but perhaps someone else will chime in with something like that.










  • Running ALSA as root had one huge benefit

    Huh? ALSA is not a sound server, but a collection of kernel components and libraries. You don’t run it.

    With PipeWire or PulseAudio, audio is bound to a user session.

    PipeWire has a system-wide mode of operation. It wasn’t well-tested when I last asked about it, but it might be worth a try.

    GTK3 broke accessibility for years.
    GTK4 released with no accessibility support at all.

    This whole article is focused on GNOME and other GTK-based desktops. The only mention of KDE Plasma at all is to say that a certain GNOME fork (MATE) isn’t like it. This seems like a rather large oversight given that Qt, upon which Plasma is built, has accessibility features built in.

    So, nearly every criticism here is not about Linux after all, but about a specific desktop family. I hope the author eventually notices that others exist, tries them, and discovers things that work better in them. (And it would be nice if they were to post a more comprehensive follow-up article, or at least rephrase this one so that it doesn’t mislead people into thinking it represents the Linux desktop ecosystem as a whole.)