Astra, Sol, Terra, and Luna are also complete nonsense that I can't keep straight. I have a reference card under my monitor to remind me which one is which.
It obviously is pretty low key on the public relations front, but it's also very active as a project and I think it would be weird to look at their commit rate and conclude that the project is dead. If Fuchsia is dead then 99% of major open source projects are dead by the same standards.
Googlebook is Android with the ChromeOS application stack ported on top of it. ChromeOS hosts Android apps in a compatibility subsystem. They basically just turned it upside-down and shook it.
ChromeOS is targeted to and adopted by large organizations like enterprises and governments and school districts, because it is extremely easy to manage and has maybe 0.2% as many headaches as Windows or Mac.
I don't really agree because it's so hard to reform a full application that's been written without regard to performance, after it's been written. You really need to pay attention from the beginning.
Yeah I don't get it, either. If the exercise relies on the assumption that the agent can't reach the "live internet", whatever that means, there are affirmative steps to realize that assumption. The fact that they failed to take those steps suggests two possibilities: they are idiots, or they think we're idiots who will fall for this marketing campaign.
They decided that instead of having an Android runtime on top of ChromeOS they would port the ChromeOS desktop features to Android. A Googlebook boots Android.
Berkeley is a hotbed of reactionary, far-right, and generally weird behavior. We've got this sex cult of course, and we have Curtis Yarvin, Michael Shellenberger, etc. Our tolerance for deviance acts as a shield that attracts self-depicted contrarians.
At my employer in 1999 we were maintaining home-grown binary modification to the Solaris kernel so that TCP segment send and receive were not O(N^2) where N was the number of addresses on the interface :-/ It was, as far as I could tell, an operating system that nobody had ever tried to use before. For anything where we could avoid Sun we used FreeBSD. One of the nice things about the free Unixes of that time was that process and thread creation or destruction were orders of magnitude faster than on Sun. To me, Sun was obviously in a lower category than Linux/FreeBSD/NetBSD.
Right before they fell face-first into the grave, they did finally ship the v20z, which was a completely reasonable way to run Solaris x86. Its management board ran Linux on PowerPC, for irony purposes.
Sure, also true that the per-CPU scheme co-evolved with the proliferation of services with thread-per-request architectures having way more TIDs than cores.
Can we stop acting like selective quoting from discovered materials gives us an unbiased and factual representation of the truth? The plaintiff is always trying to cherry-pick and distort elements from discovered material. And this is exactly why every large corporation without exception tries to train their employees to not draw conclusions of law in discoverable written materials. A computer science professor does not have the requisite knowledge to determine that some act was "theft of labor" nor the knowledge required to contextualize that "in human history".
Exactly. You want memory arenas that are hot in this CPU's caches. If your thread moves, its per-thread caches are now elsewhere. Original TCMalloc was developed in the days of 2-4 core servers. Current TCMalloc was an evolution in the context of 32+ core servers.
How much experience do you have with LLMs exactly? It would be consistent with my experience if Claude stuck in a line of python that just emits a JSON literal with no justification, potentially buried in a large program where an untrained person might not notice it. I don't even trust them if the output consists of structured data paired with source images from the PDF, because I've experienced LLMs fabricating the source rectangles to match the output. I only use tools like this by asking for programs, because as you note LLMs are good at that, and the verification process consists of tool calls to legitimate PDF manipulation tools so I have some confidence everything is above board. Even then I only do this for hobbies, not anything that matters.
> 2. Whenever a service retries but has to give up, the error it sends to its callers should never be retried. There has to be some agreement that that HTTP code will never be retried. This prevents the multiplicative factor of retry on top of retry, which is why those storms can generate so much load.
This can't really be tolerated in practice, though, because it means that one bad component somewhere in your stack, one that is able to accept and respond to requests but for whatever reason isn't able to make requests to its backends, poisons the whole stack. You can't take one backend's word for it that the failure is not localized and therefore retryable.