"300ms clean builds 100ms dirty builds" my ass did NOT comprehend how long fetching things from the internet takes (like 20ms per file), and also how long it takes to save/load 60MB from disk (like 100ms each way on my drive), and also how bad "tokio::sync::Mutex with a bunch of waiters" could be (extremely).

Going fast is not normally a thing I have to think about too hard with #rust but when I want to go this fast, with this much data, from a cold start, I guess I have to ya!

Plenty of architectural improvements left in the tank:

• lazy-load large objects instead of eagerly (this should save big on disk IO in dirty case)
• threadpool for javascript work instead of N threads (pretty tricky but almost definitely worth it)
• file-watching daemon (saves big on disk IO for database & file hashing, but fairly complex)

I was naive to think "in n out quick 15 minute build system", but this is fun regardless :3