I think this is conflating opensource-corporate and english-non-english.
If you ask american/european/english-speaking developers about coding, it will mostly be about/in the context of corporate environments rather than open source too! The majority do not actively or primarily contribute to open source projects, but instead corporate environments as well.
In an alternative timeline where the lingua franca isn't english, I can still see open source culture exist; I don't think the desire to publish and cooperate in public is an inherently "western" culture. It will also run into the same conflict of interest between Open-Source and Corporate: one prefers transparency and full-disclosure, the other prefers control in the interest of minimizing risk.
Having messed with RPG Maker formats recently, I find this fascinating because it's so much more elegant and nicer looking.
Though it seems like it's more suited to fully text based scripts. The format I was messing with was full of markers to e.g. change the facial expression of the speaker's portrait, play sound effects, etc. (mid dialogue!)
Makes me think about how script/dialogues are written and formatted internally in other mediums. Umamusume in particular stands out in my mind; it has a lot of movement and actions as the dialogue lines are spoken. Sounds silly but they really do make it feel more dynamic and alive.
It is certainly my biggest dislike factor with my stay in Germany, and I'm still struggling to come to terms with it: do I dislike it enough to compel me to move away? is this something I can accept? How much can I influence and improve things that I directly interact with?
It seeps in everywhere too, with almost all aspects.
Day-to-day with restaurants, cafe, shops. Almost all interaction feels like it's actively checked if it's in their process or job description. Shop staffs are typically disengaged and can't really help you with anything outside the normal process.
Healthcare, both receptionist and doctors. You can see the rushed service because they are only compensated for limited amount of time by the state insurance. This took me a while to figure out; the process really defines what treatment you get, with what equipments, as well as the duration, and they have to do their best with the constraints put by the process.
An example: with Wurzelkanalbehandlung, the process says (at least back then) only 1 hour of Laborkosten can be compensated by the state insurance. This means if the dentist took more than 1 hour to work on you, that would be done at their personal loss, and thus the incentive to rush the procedure.
Going private helps (they tend to be more relaxed after the mention of of Privatzahler, and gives you access to newer equipments not yet acknowledged by the state insurance processes), but you still have to research, find, and pick the right practice.
Bureaucracy, administrative. You often have to deal with clerks that just go "I just work here", the rules says this and there's nothing I can do, throws hand in the air. Goodbye, next person please!
In day-to-day work, I can also see it. New hires tend to be more into the work, and questions things, but the system does push everyone to just follow the process and not do anything more. I've seen my colleagues slowly shift into this mode, delivering what is outlined, nothing more, not questioning the intent behind the work (or at least, doing it much less than before, because the system does not incentivise that).
I don't know how much of that 6 hours build is tangled up in github workflows, but if it's a single contiguous block, you probably could make it near zero by making the self-hosted runner do only the preparation and only the final upload process (workflow_dispatch when the build is complete).
per minute billing is hard to wrap around the head
On my larger organization, we have on average 20 to 30 *active* runners during business hours. Assuming 5 on the off-hours, my napkin math says it comes down to about 10 fully-utilized-runners per month, so about 864$/mo. For the size of my organization that is honestly totally acceptable.
This is assuming 0.002$ per minute of job being actively executed. If it turns out to be 0.002$ per minute of *runner being registered* on the control plane, it would increase quite a bit. We are still using the old HorizontalRunnerAutoscaler with actions-runner-controller, with quite a pool of prewarmed runners idling to pick up a job. It would be a strong reason to use the new RunnerScaleSet (to take advantage of the reactive webhook-based scaling) and keep a very lean pool of prewarmed runners.
If you ask american/european/english-speaking developers about coding, it will mostly be about/in the context of corporate environments rather than open source too! The majority do not actively or primarily contribute to open source projects, but instead corporate environments as well.
In an alternative timeline where the lingua franca isn't english, I can still see open source culture exist; I don't think the desire to publish and cooperate in public is an inherently "western" culture. It will also run into the same conflict of interest between Open-Source and Corporate: one prefers transparency and full-disclosure, the other prefers control in the interest of minimizing risk.