1,948 karma · joined July 31, 2020
This gives the attacker access at the UEFI level and above -- they can use it to produce false attestations.
https://semiwiki.com/forum/threads/samsung-teases-16-layer-3...
Don't try to pretrain from scratch. Take an already-trained Qwen and give it new powers.
https://github.com/indexable-inc/blaze/blob/main/docs/usage....
Hey what could go wrong? You didn't really need 33% of your borrow-checking anyways.
Only one contributor with more than four commits.
Initial commit was 7 days ago. I guess now we have a "vibechecker"!
No, rationing is what you get in command/centralized economies like the USSR. In free market economies you get price explosion, like we're seeing right now with DRAM wafers.
The comments you upvote/downvote are used to calculate your "opinion similarity" to the owners. Then your upvote/downvotes are modulated by that similarity. It's a way of using other humans to amplify the opinions of the owners -- they don't have time to read all the comments, so instead they filter out those who think the same way they do and let them do it.
People got very very angry at me for pointing this out.
So I stopped doing it.
It's the worst of both worlds!
Seriously nobody advocates UTF-16. The smart people advocate UCS-2.
If you want to say that the facts are dumb, well, you can do that.
Unicode is China forcing variable-length character encodings on the rest of the world.
Diagonal wires worked everywhere at 180nm and on a few fabs at 90nm if you rotated a whole metal layer (i.e. all metal-3 wires are diagonal to the metal-2 wires) and basically nowhere beyond 90nm.
OPC killed it. Too hard to OPC the diagonal stuff. And even if you rotate an entire metal layer, the contacts between a rotated and un-rotated layer would require enormous metal enclosures.
It used to be my go-to "cheap model". I'm glad I have 4.1 now for that.
... which is a foolish mistake.
Also, they have an economic incentive to make themselves the kitchen sink.
Secondly yeah, all models have issues with foreground vs background subagents. So I just modified my harness to delete foreground subagents. No more confusion. If they need the subagent's output tokens they can read it from the session transcript.
"Take away tools" is often the best solution for model-gets-confused problems. Narrow down your toolset until there's only one way to do things, and then make it the maximally-powerful way.
IMHO you need at least 500B weights before the confabulation problem is really under control. i.e. DeepSeek 4.1 or GLM.
I admit some days I'm just lazy and throw a whole Kimi or QwenMax at it.
Aren't you glad cargo connects to the network whenever it feels like it? I just love it when my build tool does that.
There are 753 crates that drag in brotli this way: https://lib.rs/crates/curl/rev
The real killer is the oath crate. Basically every rust project using OAuth is vulnerable. That's 398 projects on crates.io plus who knows how many binaries (a lot of non-library projects don't bother publishing to crates.io).
Another scary one is "a practical HTTP client that is fun" https://lib.rs/crates/isahc used in 317 crates including sequoia. In case you wanted somebody to steal your private keys.
Databases and operating systems are inherently concurrent. They deal with concurrency sources outside the process running the Rust code. Because of this, they don't get the magical shared-xor-mutable => deterministic-concurrency benefit that Rust is famous for.
And, frankly, if you tried to make SQL/ACID shared-xor-mutable you'd completely cripple it. Databases are inherently concurrent.