I’ve migrated a lot of projects from fossil to git eventually, but I dare say they never would have made it that far, had I started out with more friction, including fighting vcs tools.

Just the other day I was starting an exploratory project, and thought: I'll just use git so I can throw this on github later. Well, silly me, it happened to contain some large binary files, and github rejected it, wanting me to use git-lfs for the big files. After half an hour of not getting it to work, I just thought screw it, I'll drop everything into fossil, and that was it. I have my issue tracker and wiki and everything, though admittedly I'll have some friction later on if I want to share this project. Not having to deal with random git-lfs errors later on when trying to merge commits with these large files is a plus, and if I ever want to, I can fast-export the repo and ingest it into git.

[1] https://ptpwebcam.org/

Octopart, etc haven't been able to accurately track inventory through this disruption.

Its simplicity also made it great to write an interpreter for, including GC. However, nowadays the focus shifted to JIT, mostly via LLVM, which leaves such free-form languages unable to compete on performance, without significant effort.

I do fondly remember the endless explorative chats with Steve Dekorte and the other language geeks on IRC!

I don't think the same is true for software "engineering," as it seems that all possible forms of process can be subverted and cargo-culted, from agile methods down to code checking. Certainly there is room to remedy some shortcomings, but SWE definitely is the engineering discipline least based in physical fact.

The physics behind simulating the buckling of a structure is always the same, we can just choose more or less crude approximations of it, but SWE in general seems a lot more diverse. I can implement that simulation in assembly or some scripting language, and attach various bits and pieces to it to manage users and data; deploy it across the cloud if need be. But, there isn't a singular, time-invariant optimal path to achieving that, and what is true today may not be true tomorrow. One can work off basic principles, like the Agile Manifesto, but how can you quantify or even certify this shifting landscape?

David Rosen pulled off quite a few little masterpieces -- his gamedev competition entries always had fantastically unique aspects. I cannot believe "Black Shades" was almost 20 years ago! (I have no affiliation, but I am glad to see https://www.wolfire.com/games is still alive and kicking!)

Lugaru and later Overgrowth have been the outcomes of what can only be called a decades long obsession with getting the player controls just right, allowing very natural and responsive control and movement, through creating emergent behaviors from first principles, resulting in a rich and natural interaction with the environment (and other characters, see the fighting mojo), in contrast to the many, many AAA titles that just constantly break the immersion through unnatural, jarring behaviors and frustrating limitations.