i wish building tooling didnt require my sandbox to give network access (why is your tool fetching tarballs from the network without letting me skip😭)
will keep trying
seeing the confusion on the quotes and replies of this tweet, maybe "ABI" is way too related to "the kernel abi" for a great amount of people, rather than "some general binary interface" like, e.g., libc's
I don't know if a lot of people have thought why this happened.
To make Linux viable for the layman, Valve had to make Proton (derived from Wine) so that Win32 API became the first and only stable ABI on Linux.
Why did Linux Distro devs not care about stable ABI historically?
dynamic linking is fine when you can control the reach of dynamic dependencies in a system in such a way that they cant interfere w/ each other
build systems/software packagers/whatever that let you have this are pretty nice and handy for quick patching w/o recomp (w/ cache)
A bitcoin private key is 256 bit, or 2^256 or this 115792089237316195423570985008687907853269984665640564039457584007913129639936
Which needless to say is a lot
>Google not wanting to bug bounty as much because of AI slop. Bug bounty nerds throwing hands everywhere
very bold coming from the very creators of big sleep
I've been extremely busy. Haven't been able to malware as much.
Here is what I saw:
- Linux security nerds big angry at some dude named Eric because he has been ignoring security things, or something, I don't know. Some drama about CopyFail and some Android stuff
- cPanel CVE destroying normies, botnets, compromises, spam spamming stuff
- Google not wanting to bug bounty as much because of AI slop. Bug bounty nerds throwing hands everywhere
- A bunch of nerds arguing about the WeezerOSINT guy, saying he's a criminal, others saying he is cool and badass
- A bunch of nerds angry at the Lunduke guy
- Will Dormann going ham sandwich on CopyFail
- More updates on those dorks who were in ALPHV but also cybersecurity negotiation people, they're cooked
- 15 year old arrested for cybercrime in France (stuff with Breached, I guess, I don't know).
- Everyone yapping about Fast16 still
- China tests spooky deep sea oceanic internet cable cutter thingy
- More NPM malware
- Apple Claude md thingie oopsie doopsie
Did I miss anything?
To start, the more “all in” on TigerStyle you go, the easier DST gets:
- static allocation (often skipped)
- assertions (sometimes skipped)
- explicit fault models (including gray failure)
- narrow interfaces (with weak expectations)
- zero dependencies
But to really do DST your simulator needs to be “Protocol-Aware”.
For example, Determinism, say in a hypervisor is powerful and important, but you really want the simulator not only to be deterministic but also to “understand” your world, your protocol, to be able to reach in and know how far it can push things, where the breaking limit is, even w.r.t. things like optimal erasure coding or strict serializability or minimizing the number of messages for a recovery path.
Then you start to be able to do things like Deterministic Performance Testing (DPT) which is where we’re exploring now.
Libghostty can now be used to fuzz TUIs, thanks to @owickstrom + @AntithesisHQ. They already found bugs in multiple including btop. I always imagined libghostty would be useful for testing TUIs, super happy to see this is both practical and valuable. https://t.co/02rVjF740v
This is another example of where speed matters! "Why does Ghostty need to be so fast?"
Well, if you're running hundreds or thousands of unit tests that each use a clean in-memory terminal, you want that to be fast. If you're fuzz testing and trying to push an unlimited amount of data through a terminal, you want that terminal to be fast.
So many people got hung up on "why does my terminal _GUI_ need to be fast" without connecting one more dot and realizing the GUI is only fast if the core is fast, and the core being fast unlocks a hell of a lot more.
Like this.
would they still have had the perf hit with some sort of warmup phase that filled the page tables beforehand to prevent tlb misses preempting the process from the fault handler? idk, interesting problem regardless