In a game that is production ready you would be going through individual assets with the person who designed them and you’d establish when to spawn and despawn them. As designers tend to go crazy and not worry about memory at all, I tend to guide them to think about memory availability in a particular scene. Really depends on the game you’re making though

You can push mirror your fork back to GitHub when you deem necessary (e.g when it’s in a good shape) and create a PR to the parent repo automatically using forgejo runner script, you’d just need to make an API token. If the goal is to automate PRs. If the goal is to not use GitHub for your forks but still continue to make PRs, you can’t work around that I think. Unless there’s a way to PR a bunch of patch files perhaps?

Yeah I can make a list of features that I’d like to have and annoyances that exist now, but I wouldn’t call it stuck in a single monitor paradigm either. Depends on what your needs are I guess!

JetBrains IDEs can be easily configured for multi monitor setups. I use Rider daily and have a couple layouts saved for different purposes that make full use of 3 monitors, never really had a problem with it. Can you be more specific about what you want to achieve?

Yeah it’s a ci/cd runner, using a tool called “act”. I self-host forgejo and the runner is a docker-in-docker container, but one could set it up with the public forgejo as well. It’s pretty neat!

Did exactly this recently and it’s been quite good. Forgejo-runner was a bit tricky to setup but overall a great experience.

It’s a reader assistance, some paid for tool that highlights parts of a word, can’t recall what it’s called…

Can’t you just install the extension (vsix is the file extension I think) package manually in vscodium?

Yeah you’re totally right. Nonetheless the use case has it’s place. People buy and use hobbyist hardware, and this is a market on its own.

Take a look at micropython, some drivers are writing in pure python, I’ve written a display driver previously

I’d probably think about switching to Graphene OS at that point

indeed, worth linking it: https://github.com/jdxcode/rtx