This "not doing well" is being three times higher than at the time of FTX collapse.

On paper, this sounds amazing. Like "out of sci-fi books" amazing. The caveat, though? I very much doubt Google has the capacity to execute this properly. And we'll get another half-baked attempt at reskinning Chromium and/or Android.

I mean, inference engine might need to get some tweaks, to support whatever compute is available. But then, if you put a few terabytes of disk for swap, and replace RAM to bigger sticks if possible, it should work? Slowly, of course, but there is no reason it should not to.

It's here, right now. I'm running quantized Qwen and Gemma on a decent, but three years old gaming rig (think RTX 3080 12GB and 32 GB RAM). Yes, it's slow, it has a small context window. But it can (given a proper harness) run through my trip photos and categorize them. It can OCR receipts and summarize spendings. It can answer simple questions, analyze code and even write code when little context is required. Probably I could get a half-decent autocomplete out of it, if I bother with VS Code integration. "128 GB VRAM on a MacBook Pro or a Strix Halo" is already a minimum viable setup for agentic coding, I think.

> And then we'll have the equilibrium we already have with the "classic cloud": you either self-host or pay for flexibility and speed.

Currently, it works exactly the other way. The cloud versions are orders of magnitude cheaper than self hosting, because sharing can utilize servers much more efficiently. Company can spend half a million bucks on a rig running GLM 5.1, and get data security, flexibility and lack of censorship, but oh it's so expensive compared to Anthropic per-seat plans.

What is the point of keeping it private? I'd bet feeding this patch to Opus and asking to look for specific TOCTOU issue fixed by the patch will make it come up with a testcase sooner or later.

Linux is open source, so every patch fixing the security bug is immediately visible to everyone. There is no workaround to that by the very design how the kernel is developed. The "embargo" people talking about is the rather stupid notion that if people keep their mouth shut and not write "THIS IS A LPE" straight in the patch description, everyone can pretend vulnerability is not leaked until the "official" message in the mailing list is sent.

This approach might have been defensible before, but in LLM era, when people have automated pipelines feeding diffs straight from the mailing lists to SotA models asking to identify probable security issues fixed by those, it is both stupid and dangerous.

And another question: has 100k$ requirement on H1Bs make any meaningful impact on applications count (e. g. to remove the lottery)?

It's so rare this thread is literally the first time I've heard about possibility of methanol poisoning from homebrewing.

Methanol poisonings happen from bootlegging, where someone in the chain of supply sells industrial methanol as an ethanol, because the first one is cheaper, easier to obtain and untaxed.

Only if this is considered a failure.

Native English speakers may not know, but for a very long time (since before automatic translation tools became adequate) pretty much all MSFT docs were machine translated to the user agent language by default. Initially they were as useless as they were hilarious - a true slop before the term was invented.

Then, if the price was pumped and the liquidity didn't match it, it'd be a perfect target to squeeze (because the market is so highly leveraged), at least one trading firm should've attempted it.

Never? For the sheer amount of moonshot bets he's doing, his track record would make any VC jealous. Zip2, PayPal, Tesla, SpaceX, Grok/xAI.

22 December 2001, American Airlines Flight 63 7 May 2002, China Northern Flight 6136 25 December 2009, Northwest Airlines Flight 253 2 February 2016, Daallo Airlines Flight 159