> 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
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.
Jeans were almost invented for this kind of thing. I'll always cringe at the idea of wearing them wet though—
"Looking to provide its sailors with durable clothing that could be worn wet or dry, the navy began in the 16th century to equip sailors with Genoese-produced denim jeans, and in doing so became one of the driving forces behind the adoption of the clothing" https://en.wikipedia.org/wiki/Genoese_navy
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.
The OpenBSD devs continue to outdo themselves for hw support. First Broadcom drivers, then Apple Silicon (working with the Asahi devs), now Qualcomm. Very impressive
This looks awesome. I had this exact problem just last week and had to write my own tool to perform the migration in go. After creating the tool I thought this must be something others would use- glad to see someone beat me to it!
I think it’s clever keep the tool simple and only copy one table at a time. My solution was to generate code based on an sql schema, but it was going to be messy and require more user introspection before the tool could be run.
Two of your 4 questions were answered in the first content block