I used to think about it a lot when I was younger because it seemed so unfair that life comes to an end. As I’ve gotten older (and closer to the inevitable) I think about it less. Hopefully you’ll get to the point you realise worrying about something you can’t change isn’t productive use of the time you have left. That doesn’t mean you shouldn’t do what you can to eat well, keep fit and put off that final reckoning as much as you can.

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.

Yes and no. A lot of the projects I work on the majority of the engineers are funded by companies which have very real commercial drivers to do so. However the fact the code itself is free (as in freedom) means that everyone benefits from the commons and as a result interesting contributions come up which aren’t on the commercial roadmap. Look at git, a source control system Linus built because he needed something to maintain Linux in and he didn’t like any of the alternatives. It solved his itch but is now the basis for a large industry of code forges with git at their heart.

While we have roadmaps for features we want they still don’t get merged until they are ready and acceptable to the upstream which makes for much more sustainable projects in the long run.

Interestingly while we have had academic contributions there are a lot more research projects that use the public code as a base but the work is never upstreamed because the focus is on getting the paper/thesis done. Code can work and prove the thing they investigating but still need significant effort to get it merged.

It’s one of the reasons I enjoy working on open source. Sure the companies that pay the bills for that maintenance might not be the ones you would work for directly but I satisfy myself that we are improving a commons that everyone can take advantage of.

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.

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?

Magic Wormhole - it’s been around awhile but it’s super useful for moving files from your internet connected server to your phone without going through multiple hops copying stuff to you local machine and finding a cable.

That’s how it starts. Before you know it you’ll be buying no-name smart bulbs from Ali Baba and investigating custom firmware for full local only control.

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.

TIL

It’s called vrms (virtual RMS) and Debian at least packages it.

Why do the $20 subscription when the API pricing is much cheaper, especially if you are trying different models out. I’m currently playing about with Gemini and that’s free (albeit rate limited).