(no title)
ZoomZoomZoom | 8 days ago
The Jakt -> Swift -> Rust pivots look like the same thing on a different level. The initial change to Swift was surely motivated by potential industry support gain (i believe it was a dubious choice from purely engineering standpoint).
It's awe-inspiring to see how a person can carve a job for himself, leverage hobbyists'/hackers' interest and contributions, attract industry attention and sponsors all while doing the thing he likes (assuming, browsers are his thing) in a controlling position.
Can't fully rationalize the feeling, but all of this makes me slightly wary. Doesn't make it less cool to observe from a side, though.
rjh29|7 days ago
The truth is more simple: he's a good engineer and leader, people recognised that and offered him sponsorships, and the project took off by itself.
ZoomZoomZoom|7 days ago
SatvikBeri|8 days ago
zamalek|8 days ago
stephen_g|7 days ago
If I recall correctly, part of this was around classes they had that replaced parts of the STL, whereas the Swift C++ interop makes assumptions about things with certain standard names.
blub|8 days ago
We’re at the point where a solid test suite and a high-quality agent can achieve impressive results in the hands of a competent coder. Yes, it will still screw up, needs careful human review and steering, etc, but there is a tangible productivity improvement. I don’t think it makes sense putting numbers on it, but for many tasks, it looks like there’s a tangible benefit.
mi_lk|8 days ago
newswasboring|8 days ago
Wary of what?
carderne|8 days ago
Long read on the topic (quite funny, covers Cluely): https://harpers.org/archive/2026/03/childs-play-sam-kriss-ai...
nix-zarathustra|7 days ago
IIRC he used to work on the Safari browser engine at Apple.
ozgrakkurt|8 days ago
LLM and rust rewrite together. And it does work so hopefully they get more attention and build it so I have an alternative browser to use