I did a quick search on the comments page for "he"+"him" and found nothing referring to foone, and was about to congratulate HN for getting it right, and then thought to scroll to the bottom of the page and found a dozen dead/autocollapsed comments, most including the wrong pronouns. At least they're where they belong.
If chunks of functionality are missing from MV3 with no available alternative, if the replacement is really at such an early stage of development like this, it would be silly not to delay mandatory adoption by another year or two. (Including requiring new extensions to be MV3 - from what I'm reading here, it sounds like you're really not ready for that and should undo it.) Please don't be another https://goomics.net/50/. It's so much worse when it happens externally in an ecosystem.
All GNU documentation is written in this format. But here they seem to have neglected the standard procedure of converting to HTML before publishing...
The number one problem with matrix in my experience is latency...it's common for loading the app or a room or message history or sending a message to take multiple seconds. I wondered if dendrite might be the solution to this, but the readme says it can handle only 10-100 users, which feels off by a couple orders of magnitude. Is the overhead of decentralization really that bad?
The community of toki pona speakers has grown to the point where there is no such thing as an authoritative source, much like a natural language. If you want to learn in depth your only option is to join a chatroom and talk to people. For intro material, there are many free options beyond the official book. https://devurandom.xyz/tokipona/ is quite good.
Hypervisor.framework (and Virtualization.framework) in macOS run a Apple written hypervisor. This hypervisor implements VirtIO for its devices and can run macOS VMs (with full graphics and hardware acceleration, at least on the M1). One could conclude that it was implemented this way to allow compatibility for macOS on different hypervisors (and also so that Linux would just work on theirs).
Speculation: I would be surprised if there isn’t a team internally working on a stripped down variant of macOS (or just Darwin + drivers?) designed for deployment as a server so that they can drop a bunch of racks of Mac Minis (or, with budget, some kind of blade arrangement with a Apple Silicon chip on it) into a datacenter and build a huge build farm (using VMs to run iOS and macOS, or jails if they ever get some kind of container setup). It would be dramatically better than having to manage x86 and all that extra bloat of average servers once you got through the growing pains. And they could guarantee security way better.
I think Apple's silicon runs a very high margin, I imagine. Will the savings from running datacenters on their own silicon be big enough to offset the lost opportunity of selling more M1?
I don’t think the demand curve is matching supply at this point, and the processors, while powerful, will be outdated in a relatively short timeframe. Utilising them in a build farm would be one way to put any excess to good use.
And for Trillion dollar firm a way to get into a big and never touched now business. The Apple server and business object aside, the m1 might be a good line of business to try. This is particular so now Apple is not controlled by intel on their product development.
The next will be the gpu market.
No need to do the extreme just the one that can handle normal server load, flight simulator, even just 2k AA game.
Someone is doing the market analysis (not selling but real market segment under analysis), really what market one can hold the trillion dollar company.
I am not sure they can do Apple car which is mainly about hydrogen or electron capacity. But server and game …
