> The commit activity might look unusual because I worked in very intense 12h/day sprints over 14 days.

That's a weird way to put it.

The commit activity looks unusual because it's a completed project whose files were individually committed in alphabetical order. There's no development history.

Good to see more hobby OS projects. I'm almost due to start another round of learning this stuff.

What have been the most helpful reference materials so far?

What's the most memorable challenge you overcame?

What's the coolest or most surprising thing you learned?

> Reading all the really, super old documentation that explains entire subsystems in amazingly technical depth

Any links?

> Maybe this is also why Smalltalk fiends are such fans.

I started getting interested in Smalltalk after I tried writing a MacOS program by calling the Objective-C runtime from Rust and had a surprisingly good time. A Smalltalk-style OO language feels like a better base layer for apps than C.

> do you think there's any appetite in people paying for this type of tool which lets you spin up infra on demand and gives you all the capabilities built so far?

(I'm not the author) The easiest way to charge for this kind of software is to make it SaaS, and I think that's pretty gross, especially for a CLI tool.

> I'm skeptical and I may just release it all as OSS

It doesn't have to be one or the other: you could sell the software under libre[1] terms, for example.

[1]: https://en.wikipedia.org/wiki/Free_software

I often go one step futher by appending a short random identifier, `{service}.{id}@{domain}`, to make it harder to guess (in case someone learned of my email address policy).

I created a little GTK program to help: https://github.com/LightAndLight/gen-alias