Dario (the founder) has a phd in biophysics, so I assume that’s why they mention biological weapons so much - it’s probably one of the things he fears the most?
Going off the recent biography of Demis Hassabis (CEO/co-founder of Deepmind, jointly won the Nobel Prize in Chemistry) it seems like he's very concerned about it as well
it has been pretty much a benchmark for memorization for a while. there is a paper on the subject somewhere.
swe bench pro public is newer, but its not live, so it will get slowly memorized as well. the private dataset is more interesting, as are the results there:
@deno team, how do secrets work for things like connecting to DBs over a tcp connection? The header find+replace won't work there, I assume. Is the plan to add some sort of vault capability?
I follow Dioxus and particularly blitz / #native on your Discord and I noticed the exact same thing too. There was a comment in a readme in Cursor's browser repo they linked mentioning taffy and I thought, hang on, it's definitely not from scratch, as they advertise. People really do believe everything they read on Twitter.
Great work by the way, blitz seems to be coming along nicely, and I even see you guys created a proto browser yourselves which is pretty cool, actually functional unlike Cursor's.
WASM for frontend, at least, has been held back by fundamental tools like bundle splitting, hot-reload, debugger symbols, asset integration, etc. We spent a lot of 2025 working on improving this. Vite and friends are really good!
I've been working on a big Dioxus project recently and am pretty happy with where WASM is now. The AI tools make working with Rust code much faster. I'm hopeful people gravitate towards WASM frameworks more now that the tools are better.
I mean you can opine about how Rust isn't suited for browser development, but as someone building a browser in Rust, I think it's just fine. If anything, Rust has been really shining in this project since Rust was designed to build a web browser.
Also I think it's a little ridiculous to build yet another new browser in a new language when so many amazing pieces are just sitting around ready for someone to use. Come contribute, we're already much further along :)
agreed about rust literally being designed to build a browser, but when it was developed there were many amazing pieces sitting around in c++ :) let the zig folks have a go at building their own ecosystem.
That's why Rust was introduced into Firefox piece by piece. The goal wasn't to rewrite firefox in Rust - just to migrate the scary bits over to a memory safe lang. You can feel a lot of that in the servo codebase, weird pointer semantics as a result of needing to be API compatible with the C++ adapters.
If I were building a company around a new browser, I'd reach for the solid stuff that can be pulled in. Our whole blitz project is designed to be modular exactly for that use-case.
> but when it was developed there were many amazing pieces sitting around in c++ :) let the zig folks have a go at building their own ecosystem.
Servo had Mozilla's backing in that endeavor though, and even then they didn't manage to ship a full browser in a decade, the problem is just that hard.
> Servo had Mozilla's backing in that endeavor though, and even then they didn't manage to ship a full browser in a decade, the problem is just that hard.
Not that hard; Ladybird, with a fraction of the resources available to the servo team, is C++ (Moving to swift soon) and they got pretty damn far.
The lack of velocity in Rust is real; it's a trade-off between velocity and safety, and Ladybird has amply demonstrated just how rapid C++ velocity can be.
And this is coming from someone who doesn't even like C++.
> Not that hard; Ladybird, with a fraction of the resources available to the servo team, is C++ (Moving to swift soon) and they got pretty damn far.
You know the saying about the first 90% and then the second 90%? Making a web browser is the fractal version of that.
> The lack of velocity in Rust is real; it's a trade-off between velocity and safety,
No it's not, Rust has in fact much higher velocity than C++, even at Mozilla which was basically a C++ shop beforehand (and a pretty good one at that).
> and Ladybird has amply demonstrated just how rapid C++ velocity can be.
No, you seem to have a misunderstanding of what servo was. Mozilla didn't use Rust yo make a safer browser, they used Rust to make a faster browser by leveraging all the cores of modern CPUs. That was the primary motive for making Rust in the first place: making multithreading tractable for humans.
As a result, the servo project aimed for SotA performance and modules were rewritten multiple time as they improved the architecture for performance (see the different iterations of Stylo or Webrender, which ended up in Firefox proper when it converged).
That's why it was apparently slow, not because of safety but because it aimed to be the first fully parallel browser (which is something enabled by Rust's safety).
You can argue that Rust has lower velocity than garbage collected language because you need to think about ownership, but not that it has lower velocity than other low-level languages: they too need to think about ownership, they simply have no static check to catch errors at compile time: every error raised by the borrow checker would be as segfault. (And Rust keeps what makes C++ already much higher velocity than C, the ability to build powerful abstractions at no performance cost).
The browser UI will likely be more of a cool demonstration of the project instead of the end goal. We want blitz to exist to help make it easier to build stuff like lightpanda. There's a whole world of interesting browser forks that could exist but don't, and being able to easily remix the browser opens the door to new stuff like AI automation, hybrid native gui frameworks, better accessibility tools, etc.
It seems like the economy is on a “K” shaped flywheel. How much worse can the economy get for the regular worker before the systems just pops? We’ve put so much speculation into an AI/tech salvation that seems premature, especially when you look at ROI vs depreciation timelines.
I’m not sure what timeline to place on that but there has to be a floor for how bad it can get for the regular man.
Shit is just expensive. Young people can’t buy houses, good jobs are drying up, and inflation isn’t stopping.
I'm sure the Fed chart is accurately measuring what it's measuring but when I was a kid in Southern California it was normal to buy a house and raise kids on a single teacher or construction worker salary. That has become nearly impossible over the past couple decades. Many others have seen similar changes in their own areas and I don't think they're being crazy when they say it has gotten much harder to finance a normal household on a normal salary.
I don't know what the disconnect is with that chart and people's observations. Is that chart controlling for number of incomes and hours worked? If a household income increases by 20% because the members are working a combined 80% more hours that's not great. Category differences in inflation might be another factor. Sure TVs and other niceties are a lot cheaper, but essentials like housing and medical care eat up a huge portion of most budgets.
Slightly overestimates. Alternatives like Truflation show it lower.
You may be thinking of Shadowstats, which is run by a crank who just takes the official numbers and adds a number he made up to them.
I don't know why cranks always think inflation is secretly higher. Deflation is a lot worse than inflation, so if you're a doomer, believing in deflation would be more effective.
The idea that CPI sucks is far from a conspiracy theory... not sure why you're trying to color it like that.
The problem is that the error integrates over time, which IMHO is why graphs like that seem to suggest our standard of living is higher than ever... when a conversation with anyone at a local bus stop will tell you the exact opposite.
It's almost impossible for the standard of living to not be higher than ever. That becomes true if you assign any value at all to new medical discoveries. Like, people have been cured of type 1 diabetes in the last year.
That chart for sure includes higher portion of double income households (because now more women are in the workforce than in the 80s). This reconciles your view with the Fed graph
Households can have more than two incomes - roommates, children who work, grandparents etc.
In practice, household sizes have gone down over time as more people live on their own, which means the income graph is lower than it otherwise would be.
As for dual income families, they're mostly a good thing that happens when women can afford to pay for childcare. That is, that book The Two-Income Trap was mostly false. This is part of the topic of Claudia Goldin's economics Nobel, the other part being that the gender wage gap is caused by motherhood interrupting women's careers.
