It is a proper monorepo, supported with turborepo. The payment system handles one-time purchases and subscriptions, as well as refunds and invoice payments.
I'll probably open-source it at some point. I found other templates lacking in certain areas, and I think this one could be valuable.

There's "100-page ML book," and another one for LLMs. Books are usually too long, but still the best way to learn IMO. I would combine a dense book with asking an AI as I go along.

This is an example of ignoring scale. It's the difference in spotting vulnerabilities in toy examples vs. in a large codebase.

I prefer specifying `js_name` to make glue code be camel cased instead of changing Rust functions. Also, not sure if wee_alloc is still a thing, or how does it compare to talc, which is newer.

Two real arguments are about how multi-language projects are harder to develop, and basically how the kernel was "fine" before Rust. The first one I agree with, the second depends.