5 ms·

Why wouldn't it be Chromium/V8-based? New browser engine is multiple developer-years of effort.

• 827a 11mo ago
  But I thought AI was supposed to be writing 90% of code by now, you're telling me building a new browser engine is still a multi-year, difficult effort?
• SeanAnderson 11mo ago
  Just seems like not a very smart long-term move to build on it. Tough to get changes upstream when the majority of engineers working on Chromium are Google devs. Lots of features you'd hope would be available in Chromium aren't there and have to be implemented manually, but then you need to keep your fork interoperating with a massive, moving target. Safe Browsing, Translate, Spellcheck, Autofill, Password Manager aren't available in Chromium and Google cut unauthorized Chromium browsers off from using Google Sync in 2021 (https://www.zdnet.com/article/google-cuts-off-other-chromium-based-browsers-from-its-sync-service/ https://www.zdnet.com/article/google-cuts-off-other-chromium...) There's probably more issues?
  • bigyabai 11mo ago
    I'm not really seeing the alternative here, though. If your main gripe with Chromium is getting patches upstream through the vendor, that's an issue with all the browser engines available to them. Gecko would be an even riskier bet than Chromium, and WebKit verges on being chronically undermaintained on Windows and Linux.