parkcedar

Where I live, the banks say that they compound interest daily, but pay interest monthly. So, I think the small interest term is just limited to a day where the error is small enough for the average person to not care.

> Lightning Fast. Local processing means instant results without internet dependency or delays. > Always Available. Works offline, on flights, in coffee shops, anywhere you write.

Two of your 4 questions were answered in the first content block

> and I don't take 'pseudocode' as an excuse

Weird hill to die on, since neither email_t nor PARSE_ERROR were defined in the sample snippets. How do you know PARSE_ERROR is not email_t?

Another example was High Sierra. They completely swapped out the file system on that release, focusing primarily on under-the-hood changes, and imo was also one of the most stable macOS releases to date.

Interested to hear your experience with HUGO- I’ve done a lot of development in Go and keen to give this a crack.

You hardly notice the binaries though, especially since gnu cmd line utils are so similar anyway. You’d expect the c libs to be similar, but they’re not really (about as different as Mac to Linux anyway).

Yes, but since it was initially created I believe a lot of it has been rewritten. Eg, the filesystem. I suspect the memory system is different these days too, since macOS handles compressed memory quite differently (though not sure how that gets implemented under the hood).

FreeBSD is like a great grandparent, related but still very different.

Mac isn’t really BSD, it’s a common misconception. It shares some of the userland code, but it’s a vastly different kernel (derived from the Mach microkernel). The userland has diverged quite significantly now too. Though, I guess it probably is closer to BSD than Linux

Excited to try this out. I recently used lit for a complex SPA (everything from routing through to page templates and smaller components). Overall I found lit just as productive as react, which was unexpected but appreciated.