This makes no sense, operationally or in code terms. It would be a huge risk and multi month hit to many people’s schedules, just to make real after the interminable debate was done.
-
-
Replying to @BrendanEich @wycats and
You can do such a move in stages. Dip your toes and back out if things are going awry.
1 reply 0 retweets 0 likes -
Still not making sense, sorry. Have you built chromium? Are you aware of all the code for telemetry and accounts login based tracking that would need to be pulled out? Edge still putting zip files out. Any real move would cost, put skin in game, have high overhead. I see ~0 odds.
1 reply 0 retweets 8 likes -
Replying to @BrendanEich @wycats and
How are you handling this on your side?
1 reply 0 retweets 0 likes -
We took 2018 getting switched to chromium, staying close to upstream for security patches, neutering or removing all the signaling. Non-trivial cost to us, not something VC funding alone would ever cover. We are best in class now IMO, but it was a piece of work. MS not there yet?
1 reply 3 retweets 10 likes -
Replying to @BrendanEich @tobie and
What I think you advocated was "fake it till you make it", but that won't help. None of {Brave, Edge, Opera, Vivaldi} would switch how they operate until the fully split, well-governed, months x 100s of people work was done. Highly non-linear! What is Fourier analysis of step fn?
1 reply 1 retweet 4 likes -
Replying to @BrendanEich @wycats and
Sorry for asking what's probably a dumb question, but what about Blink? Its boundaries with Chromium are fuzzy to me. Would it suffer from the same issues you described above?
1 reply 0 retweets 0 likes -
Blink alone is not enough! You want gmeet screen share? You want all features including WideVine DRM? You had best fork the entire codebase including the front end. Building your own FE on unstable, nonstandard, ever-shifting APIs is pure folly and we learned it on Electron. Bah!
3 replies 0 retweets 8 likes -
Replying to @BrendanEich @tobie and
Re Electron, I had naively hoped the industry would know better than to tie itself to the internal-only, ever-changing Chromium Content API. Nope. :\
2 replies 0 retweets 3 likes -
We knew better but at small scale (2015) had no choice, and at larger scale (late 2016), forked Electron (Muon), and at larger still scale (2018) forked chromium and dumped our Electron fork. Scale, why is that word repeated? What cost of capital? LOTS!
1 reply 2 retweets 3 likes
Not criticizing your decisions, to be clear. I understand the constraints.
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.