Browser engines, though? /cc @BrendanEich
-
-
5 years, maybe -- but I'm skeptical, because it'll mean perf loss on benchmarks. Want to bet? Small wager.
-
We'd have to define "big chunk" for the bet, too. Time to rewrite by hand has low empirical LOC/day bound.
-
Then people say "Hey, why are we maintaining these two different network stacks that do the same thing?"
-
And then there's a push to switch to Go. I don't expect browser teams to do the initial work at all.
-
I also could see some IoT/whatever stuff in Go, integrated with Chrome IPC, and then added to Chrome ATF.
-
Lots of WebKit-cum-Blink code to rewrite if "significant chunk" fits my def. 5 yrs is long time. Good bet!
End of conversation
New conversation -
-
-
Firefox is already shipping some Rust code, with a lot more on the way. No GC though.
-
best thing I ever heard
-
me too - I was Godfather (exec sponsor, made them an offer they couldn't refuse) of Rust at Moz.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.