It's also going to be yet another browser to support, it's not like it's going to be identical to Chrome or that Edge and IE are going to disappear overnight :D
I wonder why they didn't choose Firefox's Gecko though
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
That's a reason to go against the current! Otherwise all browsers will be the same browser in the end.
There's value into building platforms on top of the same rendering engine but there's also value into not having one single rendering engine :D
I understand the choice Brave made because they have few resources, but Microsoft is huge :D I just hope someone will write an article about the choice so I can better understand it. I'm not saying it's wrong, just that I don't have a fully formed opinion.
Electron. They have So many Apps using Electron. When MS integrates Electron in Windows (as they do with EdgeHTML for Store Apps) they would need to contribute to two engines.
That's what I hope for, also take in mind that winui has been made open-source yesterday so we might be able to see more "fluent" cross-platform interfaces some time in the future, including (hopefully) this browser
Gecko remains pretty damn impossible to embed into anything else. I suppose it's not like Microsoft wouldn't theoretically have the resources to make it happen anyways, but why put the extra effort in when it'll be less compatible and the compatibility is a primary reason they're doing it anyways?
Gecko remains pretty damn impossible to embed into anything else.
"It was updated a very long time ago" it's definitely not a good start :-D
I suppose it's not like Microsoft wouldn't theoretically have the resources to make it happen anyways
Yeah I guess
but why put the extra effort in when it'll be less compatible and the compatibility is a primary reason they're doing it anyways?
True, it's just that we risk having basically only single browser engine with just different shells.
I read people on Twitter speculating that MS will probably end up forking Chromium a few years down the road and manage their own version. Likely for the same reason why Blink was forked from WebKit.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't know how to feel about this.
It's also going to be yet another browser to support, it's not like it's going to be identical to Chrome or that Edge and IE are going to disappear overnight :D
I wonder why they didn't choose Firefox's Gecko though
My guess is marketshare. Kind of like what Brave is doing, Brave Unveils Development Plans for Upcoming 1.0 Browser Release, Including Transition to Chromium Front-End.
That's a reason to go against the current! Otherwise all browsers will be the same browser in the end.
There's value into building platforms on top of the same rendering engine but there's also value into not having one single rendering engine :D
I understand the choice Brave made because they have few resources, but Microsoft is huge :D I just hope someone will write an article about the choice so I can better understand it. I'm not saying it's wrong, just that I don't have a fully formed opinion.
Electron. They have So many Apps using Electron. When MS integrates Electron in Windows (as they do with EdgeHTML for Store Apps) they would need to contribute to two engines.
Right, I forgot about that. They already have a lot of in house knowledge around Chromium because of Electron.
I wonder if this new browser will be cross platform :D
That's what I hope for, also take in mind that winui has been made open-source yesterday so we might be able to see more "fluent" cross-platform interfaces some time in the future, including (hopefully) this browser
Gecko remains pretty damn impossible to embed into anything else. I suppose it's not like Microsoft wouldn't theoretically have the resources to make it happen anyways, but why put the extra effort in when it'll be less compatible and the compatibility is a primary reason they're doing it anyways?
"It was updated a very long time ago" it's definitely not a good start :-D
Yeah I guess
True, it's just that we risk having basically only single browser engine with just different shells.
I read people on Twitter speculating that MS will probably end up forking Chromium a few years down the road and manage their own version. Likely for the same reason why Blink was forked from WebKit.