Nope. Where I live employees' salary is included in the food prices.

gentoo with openrc works just fine for me (for docker/podman there is a separate debian machine though, as I don't want untraceable blobs from the internet in my LAN)

Recently had an electric Fiat 500 as a replacement while my car (Mazda 3) was in service and I absolutely loved how it drives. Nice consistent acceleration, immediate reaction to the throttle. Much better than the automatic transmission cars I drove before. 3 problems though:

• range (duh): I often need to drive for 280km in one go, vast majority of EVs can't do that reliably (with AC and going 130km/h). If you can survive a day on one charge it is awesome though: plug it overnight and you're ready to go in the morning
• the price of the car (it felt waaay too simple and plastic-y inside compared to 30K euro price I googled)
• big brother software on the headunit, although there is no escape from it with any new car these days

and/or getting your games from places like gog.com

I'd go for HLS due to its simplicity: just files over http(s). VPN or not - depends on your network. If your machine is accessible from the internet, just putting the files into a webserver subdirectory with a long random path and using https will be secure enough for the usecase. Can be done with an ffmpeg oneliner.

The downside of HLS is the lag (practically -- 10s or more, maybe 5 if you squeeze it hard). It is in no way realtime. Webrtc does it better (and other things too), but it is also a bigger pain to set up and forward.

Also, just in case, test that the webcam works fine if left active 24/7. I had (a cheapo) one that required a powercycle after a week or so...

Freecad is... rough. But, it has python API, and that's what I ended up using for almost all my stuff (there also was a period of using cadquery, but installing it is a horrible pain, so I gve up).

Also using onshape every now and then, but many things are just too annoying to do with a gui.

For me it's GOG first. Using lgogdownloader and wine directly (in a custom apparmor profile). No DRM, no forced updates, no annoying client that takes forever to start. Games are also dramatically much easier to isolate and sandbox this way.

If the game is not there, then yes, Steam (as a separate unix user).

Whatever works for you. Just do it. It is convenient as f when you are just starting. You can always improve incrementally later on when (if) you encounter a problem.

Too much noise/power costs to run a small thing - get a pi and run it there. Too much impct on your desktop performance - okay, buy a dedicated monster. Want to deep dive into isolating things (and VMs are too much of a hassle) - get multiple devices.

No need to spend money (maybe sponsoring more e-waste) and time until it's justified for your usecases.

Depends on your local waste service. I'd go for the "everything else" dumpster. Here in NL it is incinerated, which is a decent option for such a mix.

create graph on the UI

that's something I want to avoid

hard for me to imagine a situation where graphs need to be edited so often

the whole system is under development (trying new views, changing how the data is represented, etc), so I don't need to imagine it, I have it right in front of me ;)

Something like that, where I just write a function that spits out a numpy array or something like that and it gets plotted, would be great, but there is one thing Grafana can do and vega-altair, plotly and even matplotlib (*): a UI that allows to select a time interval to view.

So I can freely pan/zoom in/out in time, and only the required part of the data will be loaded (with something like select ... where time between X and Y under the hood). So if I look at a single day, it will only load that day, and only if I dare to zoom out too much it will spend some time loading everything from the last year.

(*) yes, you can do interactive things with matplotlib, but you don't really want to, unless you must...

To be precise, the page explains how to configure some things and how to upload the config. I also tried that.

The problem is in the dashboard jsons. They are not well documented (docs on specific plots are missing), and are a pain to edit (as any json). The grafanalib tool I mentioned tries to help with that by implementing a sort of DSL for dashboards, but it is not ideal. (edit: lost a word)