FLOSS projects can only be sustainable if their are enough shared interests able to support it through contributions of all kinds. Fortunately the code is free so that constellation of support can change over time. It’s a shame this particular line of government funding is coming to an end but others can help.

I think the most useful thing for this is hosting repos that suffer from constant DMCA takedowns. Emulators, ad-blockers, site revancers etc.

Magit is one of Emac’s many superpowers.

These are all excellent ways someone can contribute to a project. Our project website has a repo anything can contribute to to make changes, even the blog entries are statically generated pages.

I’ve been using https://containertoolbx.org/ recently to manage my “other distro” requirements. It doesn’t do anything special but works nicely as a wrapper around podman and does all the bind mounts and uid mappings so you can just enter your $HOME as though you have set up your account in a new OS.

Also the PFN page locking patches so device memory can be reliably shared with VMs (used for some of the virtio-gpu modes).

I use foot which is Wayland aware and renders Unicode fonts. Honestly I don’t need much from the terminal itself as I’m usually in tmux to deal with all the “tabs” and scrollback.

Ah that will be it. Still grey on transparent isn’t super accessible.

I’m not sure why it rendered so poorly in Lemmy. It’s a terrible colour scheme but at least I could make out the bars when I followed the link.

If you license a design from someone you’ll still be paying something. Sure there are also free implementations but they are aimed at microcontrollers, you won’t get any server class chips for free.

There is a very large corpus of FLOSS software out there serving everything from individual itches to whole industries. Any project that is important to someone’s bottom line is likely to have paid developers working on it but often alongside hobbyists.

The project I predominately work on is about 90% paid developers but from lots of different companies and organisations. Practically though the developers don’t care about the affiliation of the other developers they work with but the ideas and patches they bring to the project.

I don’t quite follow what this is. Is it a from scratch implementation of the vscode experience or a fork which has removed propriety bits and telemetry?

Is it worth raising an issue with the project? Also enable logging to see if there are any clues as to why a rescan is being done?

Syncthing should have inotify support which allows it to watch for changes rather than polling. Does that help?

I work for a company that makes money supporting FLOSS. Our members pay fairly hefty membership fees because they have a vested interest in their chips being well supported by Linux and the wider ecosystem. That money funds common projects they all benefit from all well as numerous maintainers in projects keeping those projects ticking.

The engineers on the project I mostly work on are predominantly paid to work on it. We value our hobbyist itch scratchers (~10% off contributors) but it’s commercial money that keeps those patches reviewed and flowing.

QEMU is always going to focus on emulation fidelity first and there are few shortcuts. With floating point the differences aren’t generally in the numbers but in how the NaNs and other edge cases are handled. If you want to execute FP heavy code you should be cross compiling anyway.

QEMU absolutely will use hardware floating point where it can but only when it will give the correct results. FEX and Box64 are user mode emulators which achieve their speed by avoiding emulation where they can buy thunking at API boundaries.

Btrfs never really worked out for me (I think default COW doesn’t play nice with VM images) and ext4 works great.

Pretty much. From v8.0 onwards all the extra features are indicated by id flags. Stuff that is relevant to kernel mode will generally be automatically handled by the kernel patching itself on booting up and in user space some libraries will select appropriately accelerated functions when the ISA extensions are probed. There are a bunch off advisory instructions encoded in the hint space that will be effectively NOPs on older hardware but will enhance execution if run on newer hardware.

If you want to play with newer instructions have a look at QEMUs “max” CPU.

Virt-manager isn’t super scriptable but the underlying libvirt can be controlled by virsh which is a shell interface to libvirt. You can use both at the same time, e.g. start and stop via virsh and access to gui container via virt-manager/virt-viewer.