Readit Newsedit: you might need to auth yourself as human to cloudflare on blender.org for the site to display correctly.
Deleted Comment
Programming languages which do get used are always in flux, for good reason - python is still undergoing major changes (free-threading, immutability, and others), and I'm grateful for it.
https://github.com/erikdubbelboer/brainfuck-jit/blob/master/...
After years of dealing with this (first Jenkins, then GitLab, then GitHub), my takeaway is:
* Write as much CI logic as possible in your own code. Does not really matter what you use (shell scripts, make, just, doit, mage, whatever) as long as it is proper, maintainable code.
* Invest time that your pipelines can run locally on a developer machine as well (as much as possible at least), otherwise testing/debugging pipelines becomes a nightmare.
* Avoid YAML as much as possible, period.
* Don't bind yourself to some fancy new VC-financed thing that will solve CI once and for all but needs to get monetized eventually (see: earthly, dagger, etc.)
* Always use your own runners, on-premise if possible
I fully agree with the recommendation to use maintainable code. But that effectively rules out shell scripts in my oppinion. CI shell scripts tend to become big ball of mud rather quickly as you run into the limitations of bash. I think most devs only have superficial knowledge of shell scripts, so do yourself a favor and skip them and go straight to whatever language your team is comfortable with.
I much more strongly suspect it was "we're going to hire one person to do the work of three" and the result was "get it working as quick as I can".
That’s certainly what it looks like. When I first tried the game, before getting a refund shortly after, my first thought was “wtf, did they accidentally ship an old build?”. The UI feels so u finished, lacking feedback and visual clarity.