4 ms·

edge is just a front-end using the googel Big Tech web engine from google. If they customize the web engine, it's only a posture to hide the fact that they were

edge is just a front-end using the googel Big Tech web engine from google. If they customize the web engine, it's only a posture to hide the fact that they were unable to code their own in spite of their billions. That said, they are big tech, they are all and the same.

3cats-in-a-coat 3y ago
It doesn't matter who wrote the engine. If it did, they wouldn't replace it. It's about control.
fifticon 3y ago
To phrase what another said in a different way/take: They don't care about whether they themselves are the source of the source-code. What matters to them is the ability to inject their control and telemetry in the user's pipeline, on top of "chrome". This is particularly why I don't want to use Edge, and don't want them to force me to use edge. It is currently interesting, the level of violence you have to resort to, to 'uninstall' edge. It feels very win95-98-dejavu again, where the browser has been welded so thoroughly into the OS, that you need dynamite to dislodge it. As I understand it, the leverage we still have to disable it, is founded on the requirements for windows enterprise, since enterprise companies will not tolerate such bullshit.
FrustratedMonky 3y ago
Safari also forked from Chrome. Not just MS Edge. There was a joint collaboration between a lot of companies on 'chromium' (wasn't it webkit before?) and then that relationship soured and each forked it to their own browser. (I think Apple forked it first). It wasn't like the 'engine' was just some small open source project with beautiful code that MS stole. I also think you are little conflating the front end renderer, from 'web engine'. MS doesn't use the Google search engine. Edit>> Had order wrong. Apple and Google were working together on WebKit. But Google forked off first (blink). Safari continued on with WebKit. Google eventually re-branded Chromium, then MS Edge used Chromium. The point being, this was not a small indie open source project that MS stole as some anti-MS comments kind of hint at. All 3 big players were putting engineering time into these engines. This cartoon diagram might help. Wiki has a more detailed one. https://twitter.com/vladquant/status/1492181669788356611/photo/1 https://twitter.com/vladquant/status/1492181669788356611/pho...
- teddyh 3y ago
  > Safari also forked from Chrome. No. Apple created Safari using WebKit (an Apple fork of KHTML). It was Chrome which was created based on WebKit (and eventually Google forked Webkit into Blink).
- jamil7 3y ago
  Safari was not forked from Chrome. Safari's engine, WebKit is an open-source browser engine originally forked from KHTML/KJS. Chrome's current engine, Blink is a fork of this.
  - FrustratedMonky 3y ago
    I just meant that they all worked on the same engine. Who forked who, or how's on first. Doesn't change the point, that all 3 big players were all working on same engine (fork of same), so it wasn't MS 'stealing' some small indie open source project. At one point in time, Apple and Google were both working on this, and I had order wrong, Google was the one that forked first to go off and do their own thing that became Chromium, which then went on to be used by Edge. And Safari continued on with different fork, (or maybe trunk? it has split so many times, not really sure how is forking who). "" On April 3, 2013, Google announced that it would produce a fork of WebKit's WebCore component, to be named Blink. Chrome's developers decided on the fork to allow greater freedom in implementing WebCore's features in the browser without causing conflicts upstream, and to allow simplifying its codebase by removing code for WebCore components unused by Chrome. In relation to Opera Software's announcement earlier in the year that it would switch to WebKit by means of the Chromium codebase, it was confirmed that the Opera web browser would also switch to Blink.[44] Following the announcement, WebKit developers began discussions on removing Chrome-specific code from the engine to streamline its codebase.[80] WebKit no longer has any Chrome specific code (e.g., buildsystem, V8 JavaScript engine hooks, platform code, etc.). ""
- FrustratedMonky 3y ago
  Not sure why original post was down-arrowed. Here are Wiki pages to read up on the subject. https://en.wikipedia.org/wiki/Browser_wars https://en.wikipedia.org/wiki/Browser_wars https://en.wikipedia.org/wiki/History_of_the_web_browser https://en.wikipedia.org/wiki/History_of_the_web_browser https://en.wikipedia.org/wiki/Comparison_of_web_browsers https://en.wikipedia.org/wiki/Comparison_of_web_browsers

3cats-in-a-coat 3y ago

It doesn't matter who wrote the engine. If it did, they wouldn't replace it. It's about control.

fifticon 3y ago

To phrase what another said in a different way/take: They don't care about whether they themselves are the source of the source-code. What matters to them is the ability to inject their control and telemetry in the user's pipeline, on top of "chrome". This is particularly why I don't want to use Edge, and don't want them to force me to use edge. It is currently interesting, the level of violence you have to resort to, to 'uninstall' edge. It feels very win95-98-dejavu again, where the browser has been welded so thoroughly into the OS, that you need dynamite to dislodge it. As I understand it, the leverage we still have to disable it, is founded on the requirements for windows enterprise, since enterprise companies will not tolerate such bullshit.

FrustratedMonky 3y ago

Safari also forked from Chrome. Not just MS Edge. There was a joint collaboration between a lot of companies on 'chromium' (wasn't it webkit before?) and then that relationship soured and each forked it to their own browser. (I think Apple forked it first). It wasn't like the 'engine' was just some small open source project with beautiful code that MS stole. I also think you are little conflating the front end renderer, from 'web engine'. MS doesn't use the Google search engine. Edit>> Had order wrong. Apple and Google were working together on WebKit. But Google forked off first (blink). Safari continued on with WebKit. Google eventually re-branded Chromium, then MS Edge used Chromium. The point being, this was not a small indie open source project that MS stole as some anti-MS comments kind of hint at. All 3 big players were putting engineering time into these engines. This cartoon diagram might help. Wiki has a more detailed one. https://twitter.com/vladquant/status/1492181669788356611/photo/1 https://twitter.com/vladquant/status/1492181669788356611/pho...

teddyh 3y ago
> Safari also forked from Chrome. No. Apple created Safari using WebKit (an Apple fork of KHTML). It was Chrome which was created based on WebKit (and eventually Google forked Webkit into Blink).
jamil7 3y ago
Safari was not forked from Chrome. Safari's engine, WebKit is an open-source browser engine originally forked from KHTML/KJS. Chrome's current engine, Blink is a fork of this.
- FrustratedMonky 3y ago
  I just meant that they all worked on the same engine. Who forked who, or how's on first. Doesn't change the point, that all 3 big players were all working on same engine (fork of same), so it wasn't MS 'stealing' some small indie open source project. At one point in time, Apple and Google were both working on this, and I had order wrong, Google was the one that forked first to go off and do their own thing that became Chromium, which then went on to be used by Edge. And Safari continued on with different fork, (or maybe trunk? it has split so many times, not really sure how is forking who). "" On April 3, 2013, Google announced that it would produce a fork of WebKit's WebCore component, to be named Blink. Chrome's developers decided on the fork to allow greater freedom in implementing WebCore's features in the browser without causing conflicts upstream, and to allow simplifying its codebase by removing code for WebCore components unused by Chrome. In relation to Opera Software's announcement earlier in the year that it would switch to WebKit by means of the Chromium codebase, it was confirmed that the Opera web browser would also switch to Blink.[44] Following the announcement, WebKit developers began discussions on removing Chrome-specific code from the engine to streamline its codebase.[80] WebKit no longer has any Chrome specific code (e.g., buildsystem, V8 JavaScript engine hooks, platform code, etc.). ""
FrustratedMonky 3y ago
Not sure why original post was down-arrowed. Here are Wiki pages to read up on the subject. https://en.wikipedia.org/wiki/Browser_wars https://en.wikipedia.org/wiki/Browser_wars https://en.wikipedia.org/wiki/History_of_the_web_browser https://en.wikipedia.org/wiki/History_of_the_web_browser https://en.wikipedia.org/wiki/Comparison_of_web_browsers https://en.wikipedia.org/wiki/Comparison_of_web_browsers