4 ms·

Mozilla's decision makes a lot of economic sense. They got rid of projects requiring lots of engineering effort with negligible benefits for the company or for

by blub 6y ago

Mozilla's decision makes a lot of economic sense. They got rid of projects requiring lots of engineering effort with negligible benefits for the company or for the internet or for our privacy. I'm not sure at this point if it makes sense for them to keep the Firefox code base or give up, switch to Chromium and focus on what they do best - spy less on us than Google. When Microsoft gave up anyone paying attention knew this was coming. The only company that can still afford to develop a Chromium competitor is Apple. I hope they're not forced by the masses of web developers to switch to Chromium too.

cordite 6y ago
It’s still WebKit under the hood isn’t it? The JS engines are different though
- pkilgore 6y ago
  HTML engine was forked from Webkit. It's called blink now, and from what I've read the fork was long enough ago to consider them separate pieces of software.
- andrewflnr 6y ago
  No, IIRC Firefox's render engine is called Gecko, and it's a completely separate (older I believe) lineage from Webkit. Ed: I may have misunderstood which "it's" you were referring to. Oh well.
  - cordite 6y ago
    I meant between Safari and Chrome. Saying Apple maintains their own, yet they share tech.
- paavohtl 6y ago
  Chrome's rendering engine (Blink [1]) was hard forked from WebKit in 2013. [1] https://en.wikipedia.org/wiki/Blink_(browser_engine) https://en.wikipedia.org/wiki/Blink_(browser_engine)
gruez 6y ago
>They got rid of projects requiring lots of engineering effort with negligible benefits for [...] the internet or for our privacy. what? https://twitter.com/MichalPurzynski/status/1293220570885062657 https://twitter.com/MichalPurzynski/status/12932205708850626...
- 1MachineElf 6y ago
  Within the framework proposed by the parent comment, these guys would be unnecessary because Mozilla would switch to Chromium. (Please don't downvote me, I'm just trying to flesh out the exact meaning of that statement.)
- kbrosnan 6y ago
  https://twitter.com/gcpascutto/status/1293519587967983616 https://twitter.com/gcpascutto/status/1293519587967983616

by blub 6y ago

cordite 6y ago

It’s still WebKit under the hood isn’t it? The JS engines are different though

pkilgore 6y ago
HTML engine was forked from Webkit. It's called blink now, and from what I've read the fork was long enough ago to consider them separate pieces of software.
andrewflnr 6y ago
No, IIRC Firefox's render engine is called Gecko, and it's a completely separate (older I believe) lineage from Webkit. Ed: I may have misunderstood which "it's" you were referring to. Oh well.
- cordite 6y ago
  I meant between Safari and Chrome. Saying Apple maintains their own, yet they share tech.
paavohtl 6y ago
Chrome's rendering engine (Blink [1]) was hard forked from WebKit in 2013. [1] https://en.wikipedia.org/wiki/Blink_(browser_engine) https://en.wikipedia.org/wiki/Blink_(browser_engine)

gruez 6y ago

>They got rid of projects requiring lots of engineering effort with negligible benefits for [...] the internet or for our privacy. what? https://twitter.com/MichalPurzynski/status/1293220570885062657 https://twitter.com/MichalPurzynski/status/12932205708850626...

1MachineElf 6y ago
Within the framework proposed by the parent comment, these guys would be unnecessary because Mozilla would switch to Chromium. (Please don't downvote me, I'm just trying to flesh out the exact meaning of that statement.)
kbrosnan 6y ago
https://twitter.com/gcpascutto/status/1293519587967983616 https://twitter.com/gcpascutto/status/1293519587967983616