1,204 karma · joined March 24, 2017
reach me at sam at the domain mentioned above, or github.com/sgammon
It also takes a lot to do anything with a 1T+ parameter model. Arguably there is still an immense capital moat. So I'm not sure it would even have the effect the author intends.
Somehow this plan manages to lean into every single bad outcome
HarfBuzz wasn't ported to C++ until 2010. I don't know the entire constellation of libs Chrome would use if it was designed in C++ today, but I bet a lot of them didn't exist before Chrome or were even created partly as a downstream byproduct of Chromium.
In other ecosystems: if Chrome were designed in Rust in 2008, there would be no crates.io to pull from. There would be no NPM, since Node followed V8/Chrome's invention in 2009. Maven Central had ~50K packages in 2009[2], which was a lot back then. In 2026, Maven Central hosts over 3 million.
Those other businesses aren’t any less valid, of course. They just aren’t software businesses. They are businesses that (quite sensibly) use software.
Chrome’s original design definitely predates our current rich ecosystem. Plus, V8 and Chrome’s performance profile are demanding enough that there would be a pretty high bar for those dependencies anyway.
(1) adopts existing tech and improves, rather than a greenfield project with worse compat
(2) the way it uses existing node mechanisms to implement itself (+oxc) is very smart
(3) i like that the node.js-forever crowd has a way to use the newest stuff
I see
> > can’t live up to owning it.
> ?
Dagger, the DI framework, is very popular, supported by Google, and the primary way to do DI on Android (for many). It is not going anywhere. It is unlikely that this tool or product will create a bigger audience. Therefore, it might never "live up to the name," compared to the benchmark set by current Dagger. It's a simple concept.
Android is the most popular operating system on earth. Names can overlap but you shouldn’t choose one where you can’t live up to owning it.