Founder @ alias-research | cargo-rail | rscrypto | privacy advocate | Member @ Zed Guild 🦀

USA
May the bridges we burn light the way.
4
38
AWS being here is a crime
Replying to @alexlavaee
I’ve used Verus for a while. It’s getting so good. I’m glad to see someone talking about it here!
1
@OpenAI your models are not usable. They’re the worst in the industry all of a sudden.
Replying to @DeGatchi
😂
1
Replying to @_jzhao
Damn, this is really important work. What does resource consumption look like?
alias retweeted
I spent some time off reading some papers and thought that I could improve upon what was previously the world's fastest CRDT Introducing eg-strider: a set of improvements on top of Eg-walker that result in significantly better performance on every measurable axis jzhao.xyz/posts/eg-strider github.com/jackyzha0/eg-stri… (now featuring exclusive twitter language balls benchmark visualizations)
15
23
281
alias retweeted
v1 ci is half the price of blacksmith lol
2
1
23
Replying to @xav_db
Hey, cache and I have talked about this in one way or another for a long time. Let’s talk, man.
Replying to @FrancisPSantora
Curious, what did you wind up investing in? Anything standout?
1
Vector has redeveloped its IEEE 11073 SDC stack in Rust, for medical device networking. 🦀 SDC, Service-oriented Device Connectivity, is a family of standards within IEEE 11073. It lets point-of-care medical devices from different vendors discover each other, exchange measurements, states and alarms, and expose their functions as standardized services. Vector unveiled what it calls the first Rust-based SDC stack at its Medical Engineering Symposium on October 15. It is expected to be available in the first quarter of 2027. Why Rust, as Vector puts it: → Memory and type safety help prevent common memory-handling errors during development → That can reduce certain causes of runtime errors and memory-related security vulnerabilities → For safety-critical devices, it is described as a solid foundation for reliability and cybersecurity requirements On integration: → The stack can be used from C and C++ applications through a foreign function interface → Manufacturers do not need to port existing application software to Rust → The architecture is designed to work across different hardware and operating systems On performance, Vector claims significantly better results, credited to optimized XML message processing and more efficient management of the device data structure. No numbers were given. A few things worth noting: → Vector's press release does not mention any certification or regulatory approval. One trade-press headline says the stack "qualifies for medical devices", but its text does not name a qualification either → The stack is not released yet → All claims are the vendor's own. No benchmarks, customers or toolchain details were given Still, a notable signal: a long-established automotive and medical tooling vendor is choosing Rust for a protocol stack intended to run inside medical devices. 🔗 vector.com/en/company/press/… #RustLang #MedTech #Embedded #Safety
1
8
Replying to @_marwanad
Interesting. I’m super interested in auditing it - link? Is it open?
1
1
Replying to @axboe
The dude that created the challenge is great. His social media is sharp; fun. He’s a decent engineer.
6
Replying to @mgill25
So many of us.
Replying to @NickADobos
I don’t see rebuilding as a problem but an opportunity. It will have provide massive benefits to all. It needs to start sooner rather than later though.
Replying to @boredGenius
Man, this has trouble written all over it. Haha
alias retweeted
How to find ALL PHP bugs: 1. Compile code (e.g. to RISC-V, x86, LLVM IR) 2. Vibe prove ASAN and non-ASAN versions have same behavior across all inputs. Hard, but Claude can do it! 3. Find a LOT of bugs Super proud of our work. A big step towards finding ALL memory safety bugs
New on our Frontier Red Team blog: using Claude to formally verify software at large scale. Formal verification can prove that code is free of certain bugs, but historically it has only been feasible for small codebases (or required a lot of expert time). With AI models, however, this is beginning to change. In collaboration with @theoremlabs, we used Claude to prove security properties in over one hundred real-world open-source libraries over the span of a few weeks. Read our research in full here: anthropic.com/research/forma…
24
61
1,190
The most vulnerable companies in software today are those selling pure convenience. If you ship an abstraction on top of AWS, Azure, GCP, or an OSS database... you are vulnerable. You should be actively deploying capital to get off the hyperscaler needle (be brave) and funding research to ship a genuinely novel product. I'd go as far as saying you're already seeing it on the books. AI is going to remove the willingness to pay for that abstraction.
2
5
Replying to @rauchg
You’re missing something… the margins.
Replying to @evanjconrad
This is called the invisible hand and it’s healthy. I know that people don’t want to hear it, but this is how progress is pushed. The margins in the middle will go first. It’s just how it works.
4