Founder @ alias-research | cargo-rail | rscrypto | privacy advocate | Member @ Zed Guild 🦀
USA
Joined May 2023
- Tweets12.5K
- Following3.3K
- Followers838
- Likes21.4K
I know the numbers in Anthropic’s S1 are exciting, but this could seriously backfire. They must have some kind of “too big to fail” ideas because if the cost of AI comes down (highly likely) to the consumer or a competitor ships a major improvement the can’t reach… they’re fucked.
I mean, if Google, Microsoft, Amazon, or XAI ship a model that cheap enough and dominate… Anthropic is going to bleed.
The major investors, all the same people, will eat them alive.
alias retweeted
We (actually) KILLED Palantir this time!!!
New updates, better ontology generation, cloud service, and smarter agents!
You can deploy it locally here: github.com/HelixDB/helix-fou…
or use the cloud: foundry.helix-db.com
The way we develop has to evolve. I’m so tired of following these legacy standards or systems when none of it applies to our actual experience anymore.
Software is in a super cool place. We can basically start over and learn from our mistakes. We can develop three iterations at once and toss the failures.
alias retweeted
USearch v3 is ready for a design-partner preview!
3 years ago, I released USearch v2. It became my first widely deployed piece of software.
It grew to over 4’000 GitHub stars, a number unimaginable to me back then. Together with my complementary projects, that’s 17’000 stars today. The open-source infrastructure behemoths shipping these libraries by default, like ClickHouse & ScyllaDB, collectively account for over 550’000 stars. Almost 800’000 including opt-in integrations 🤯
Thank you to everyone who shipped, starred, or argued with this code! I know I can be slow to respond, and I appreciate your patience.
With help from AI agents, compute from neocloud partners and a lot of user feedback, USearch v3 finally has a release candidate. Only 1’000 days of work later 🫠
USearch v3 stays open-source, Apache 2.0, free for everyone, from open-source giants to neolabs, hyperscalers, government agencies, & even mobile publishers!
Still, I’ve seen many times how paying for an integrated software experience can work better and cost less than getting the software for free — and be in everyone’s best interest. So I want to take a page from ClickHouse and Databricks, two organizations that reshaped commercial analytics infrastructure over the past decade by building businesses around open-source foundations.
I want to do the same for Search: keep the infrastructure open and productize the experience around it.
Before putting a major breaking release on “main” branch and launching an integrated offering around it, I want to make the transition as smooth as possible for my users.
So I’m inviting a few design partners to join me in final benchmarking and help shape the UX and C ABI before the public release. Your workloads should have a say in what ships.
I have no doubt USearch v3 will be a “scale unlocker” for many organizations reliant on Search. With a little creativity and collaboration, it can become a “capability unlocker” as well.
If you’re working at a frontier intelligence lab, in autonomous driving, or in life sciences, and managing 100+ TB of data, DM me with a brief description of your workload. I’d love to collaborate!
ALT github.com/unum-cloud github.com/ashvardanian
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)
alias retweeted
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
The dude that created the challenge is great. His social media is sharp; fun. He’s a decent engineer.