With Gitea/Forgejo you can run a local actions executor, which builds the images, pushes to gitea’s image registry, and using a script pulls them on the other side and restarts them. Worked fine in our small startup.

+1 for Pocketbook

Never had any issues with it whatsoever.

The device works great with Calibre.

There is some other functionality that I did not use.

Still, if legal, one would “boil” (not sure what the term is for oil soluble?) a kilo with no issue.

Same. Really happy with it.

I started doing exactly this. Write a bunch of functions, that may end up in different systems, on different machines, even. This allows you to define the interfaces, figure out data dependencies, and so on.

The code may be runnable, just printing out some statements. Then I copy blocks of it to the place where it will belong.

It’s more of a thinking tool, than “actual code”.

You’re right, this ageism is stupid. Common lisp is probably its contemporary, yet is great. Cobol does seem like a nightmare though.

I have set up forgejo, which is a fork of gitea. It’s a git forge, but its ticketing system is quite good.

It’s not that they are separated on the chart, but that they are comparable (on both axes), that impressed me.

I know you asked about VMs, but fwiw there are GPU-capable containers now: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html

Used one of these and the setup is as easy as it sounds. It can run Houdini, Stable Diffusion.

Fair enough, i thought it should be noted. The difference was significant at times.

Same here, SMB was significantly slower in our organization than NFS.

Matrix does support voice, and I found the quality to be amazing.

Another reason to use libraries is communication. Would you prefer to receive a GitCommitResult in your code, or have to parse the stdout of the subprocess? If you need complex communication with the other program, then it needs to provide rpc or some other form of inter-process communication. A library avoids this issue.

Concepts like Reactive programming are widely used in web/UI contexts. The problem of connecting a UI to an underlying data set is not trivial. Several frameworks deal with this.

As was already said, concerns like Accessibility are studied academically. They have more to do with user experience than the technology, so not sure if they match your question.