I think the WINE project was maintaining a fork of Mono that was used to support running certain Windows applications:
So in addition to translating traditional WIN32 system calls, WINE also supports .NET applications, which a number of Windows programs require.
Coincidentally, I received a firmware (EFI) update from Dell today via LVFS. Really nice that it works so smoothly on native Linux (no more manually downloading firmware to USB drives, or relying on Windows).
The reasons for this shift in budget away from funding Free Software and the NGI initiative seems to be an allocation of more funds for AI, leaving internet infrastructure by the wayside. Meanwhile, the EC has thus far declined to comment to share its official reasoning for striking this funding from its budget.
Sigh. It appears that they are chasing after the latest “shiny” thing instead of investing in existing infrastructure. Not surprising, but disappointing.
+1 For xournal++. That is what I usually use for annotating slides and drawing with my wacom tablet.
What are your thoughts on SerenityOS?
I currently use Ubuntu for all my machines (desktops, laptops, and servers), but I used to use Void Linux on my machines for about 6 years, including on a couple of VPSes. Since you are familiar with Void Linux, you could stick with that and just use Docker/Podman for the individual services such as Matrix, Mastodon, etc.
In regards to Debian, while the packages are somewhat frozen, they do get security updates and backports by the Debian security team:
https://www.debian.org/security/
There is even a LTS version of Debian that will continue backporting security updates:
Good luck!
Not a bad list. Off the top of my head, I would say it is missing two things:
The “Introduction to Operating Systems” link no longer works (redirects to “Autonomous Systems” courses). Instead, I would recommend using Operating Systems: Three Easy Pieces, which is the textbook I use in my OS course.
Finally, something like The Missing Semester of Your CS Education would also be a nice extra.
I’m not so sure… for the following reasons:
Despite using a version of the Linux kernel in ChromeOS, Chromebooks don’t always have the best hardware (ie. driver) support from the mainline kernel used by most distributions. That’s why there are niche distributions like GalliumOS which provide tweaks to support the touchpad and audio devices in many Chromebooks. It’s similar to how Android is Linux, but it’s not standard Linux as we are familiar with (so the hardware support is different).
Many Chromebooks have really poor specs: low-wattage CPUs, small amounts of storage, low amounts of RAM. While they may be newer, they are actually probably less performant than older laptops. This has changed in recent years with the new Chromebook plus program (or whatever it is called) which mandates a reasonable set of baseline features, but that is talking about current Chromebooks and not the ones from the COVID era.
Related to the previous point, many Chromebooks are not serviceable or upgradeable while Thinkpads and some recent laptops are. You are unlikely to open up a Chromebook and be able to replace say the RAM or SSD, which would be a show stopper for a lot of people that like Thinkpads.
So… unfortunately, I think this take is a bit of a miss and I dont’ really see it happening. I would be happy to be proven wrong though since my kids have two Chromebooks from the COVID era :}
If you want something graphical to install a single deb, you can install gdebi
:
https://itsfoss.com/gdebi-default-ubuntu-software-center/
With this installed, anytime you download a deb, it will open the deb in gdebi
and allow you to install the package graphically.
No, most likely Pipewire would be used to implement the protocol for various compositors.
Think of the protocols as high-level descriptions of interfaces (or designs) that specify what needs to be implemented to support a particular feature (in this case capturing images of a “screen”). Looking at this one, it describes a ext_image_capture_source_v1
object that has various methods such as create_source
and destroy
. Different compositors could then implement or support this interface with whatever technology they wish (most will rely on Pipewire).
This is already the case with the existing screensharing protocol. For instance wlroots uses pipewire buffers in xdg-desktop-portal-wlr.
I think you meant Pop!_OS (is developed by System76). TuxedoOS is developed by Tuxedo Computers, which is a European Linux focused hardware company.
That said, the point stands… there are hardware companies making Linux supported devices.