AFAIK, Firefox is not Chrome-based anywhere.
On iOS it uses whatever iOS provides for webview - as does Chrome on iOS.
Firefox and Safari is now the only supported mainstream browsers that has their own rendering engines. Firefox is the only that has their own rendering engine and is cross platform. It is also open source.
Interestingly safaris rendering engine is open source and cross platform, but the browser is not. Lots of linux-focused browsers (konquerer, gnome web, surf) and most embedded browsers (nintendo ds & switch, playstation) use webkit. Also some user interfaces (like WebOS, which is running all of LG's TVs and smart refrigerators) use webkit as their renderer.
https://en.wikipedia.org/wiki/File:Timeline_of_web_browsers....
https://en.wikipedia.org/wiki/Timeline_of_web_browsers has tables as well.
Not technically "Chrome-based", but Firefox draws graphics using Chrome's Skia graphics engine.
Firefox is not completely independent from Chrome.
In any case, i thought chrome used libnss which is a mozilla library, so you could say the reverse as well.
(Which is similar to how K8S abuses ip-tables and makes it useless for other ends, and makes you install a dedicated firewall in front of your ingress path, but let's not digress).
On the other hand, Firefox is neither chromium based, nor is a cousin of it. It's a completely different codebase, inherited from Netscape days and evolved up to this point.
As another test point, Firefox doesn't even blink at a symmetric gigabit connection going at full speed (my network is capped by my NIC, the pipe is way fatter).
Unfortunately the security industry has proven the why threads are a bad ideas for applications when security is a top concern.
Same applies to dynamically loaded code as plugins, where the host application takes the blame for all instabilty and exploits they introduce.
If you need security, you need isolation. If you want hardware-level isolation, you need processes. That's normal.
My disagreement with Google's applications are how they're behaving like they're the only running processes on the system itself. I'm pretty aware that some of the most performant or secure things doesn't have the prettiest implementation on paper.
I believe the default behavior is "Coalesce tabs into the same content process if they're from the same trust domain".
Then you can make it more aggressive like "Don't coalesce tabs ever" or less aggressive like "Just have one content process". I think.
I'm not sure how Firefox decides when to spawn new processes. I know they have one GPU process and then multiple untrusted "content processes" that can touch untrusted data but can't touch the GPU.
I don't mind it. It's a trade-off between security and overhead. The IPC is pretty efficient and the page cache in both Windows and Linux _should_ mean that all the code pages are shared between all content processes.
Static pages actually feel light to me. I think crappy webapps make the web slow, not browser security.
(inb4 I'm replying to someone who works on the Firefox IPC team or something lol)
The danger and joy of commenting on HN!
Even if I was working on Firefox/Chrome/whatever, I'd not be mad at someone who doesn't know something very well. Why should I? We're just conversing here.
Also, I've been very wrong here at times, and this improved my conversation / discussion skills a great deal.
So, don't worry, and comment away.
FWIW Firefox under Linux (Firefox Browser 100.0.2 (64-bit)) behaves pretty much the same as Chrome. The speed raises quickly to 5-8Gb/s, then the UI starts choking, and the shown speed drops to 500Mb/s. It could be that there's some scheduling limit or other bottleneck hit in the OS itself, assuming these are different codebases (are they?).
However, you can test the limits of Linux by installing CLI version of Speedtest and hitting a nearby server.
The bottleneck maybe in the browser itself, or in your graphics stack, too.
Linux can do pretty amazing things in the network department, otherwise 100Gbps Infiniband cards wouldn't be possible at Linux servers, yet we have them on our systems.
And yes, Chrome and Firefox are way different browsers. I can confidently say this, because I'm using Firefox since it's called Netscape 6.0 (and Mozilla in Knoppix).
Also, Infiniband can directly RDMA to and from MPI processes for making "remote memory local", allowing very low latencies and high performance in HPC environments.
I also like this post from Cloudflare [1]. I've read it completely, but the specifics are lost on me since I'm not directly concerned with the network part of our system.
[0]: https://medium.com/@penberg/on-kernel-bypass-networking-and-...
[1]: https://blog.cloudflare.com/how-to-receive-a-million-packets...
Totally tangential - it looks like io_uring is evolving beyond just io and into an alternate syscall interface, which is pretty neat imho.
Mozilla suite/seamonkey isn't usually considered the same as firefox, although obviously related.
Firefox 0.8 did not have netscape branding http://theseblog.free.fr/firefox-0.8.jpg
I know. Firefox was not even an idea when Netscape 6 was released. However, inverse is true. Firefox is based on Netscape. It's just branched off actually. It started as a pared down version of SeaMonkey apparently.
The thing I was remembering from Knoppix 3.x days was "Mozilla Navigator" of SeaMonkey/Mozilla Suite, which is even older than Firefox, and discontinued 3 years later. I just booted the CD to look at it.
At the end of the day, Firefox is just Netscape Navigator, evolved.
> In March 1998, Netscape released most of the code base for its popular Netscape Communicator suite under an open source license. The name of the application developed from this would be Mozilla, coordinated by the newly created Mozilla Organization https://en.wikipedia.org/wiki/Mozilla_Application_Suite#Hist...
Netscape Communicator (or Netscape 4) was released in 1997, so If we are tracing lineage, I'd say Firefox has a 2 year head start.
Optics: To ISP: Flexoptics (https://www.flexoptix.net/de/p-b1625g-10-ad.html?co10426=972...), Router-PC: https://mikrotik.com/product/S-3553LC20D
Router: Mikrotik CCR-2004 - https://mikrotik.com/product/ccr2004_1g_12s_2xs - warning: it's good to up to ~20Gb/s one way. It can handle ~25Gb/s down, but only ~18Gb/s up, and with IPv6 the max seems to be ~10Gb/s any direction.
If Mikrotik is something you're comfortable using you can also take a look at https://mikrotik.com/product/ccr2216_1g_12xs_2xq - it's more expensive (~2500EUR), but should handle 25Gb/s easily.
With it in the way I get ~15-20Gb/s
$ iperf3 -l 1M --window 64M -P10 -c speedtest.init7.net
..
[SUM] 0.00-1.00 sec 1.87 GBytes 16.0 Gbits/sec 181406
$ iperf3 -R -l 1M --window 64M -P10 -c speedtest.init7.net
..
[SUM] 0.00-1.00 sec 2.29 GBytes 19.6 Gbits/secTurned out windows 7 or the NICs needed a lot of tuning to work well. There was alot of freezing and other fail.
But alas, they do not, lol. They just use no-cache on the query which will not prevent the browser from storing the data.
Firefox only uses Webkit on iOS, due to Apple requirements. It uses Gecko everywhere else. And I don't think it's ever been Safari-based anywhere.
> Firefox is only Chrome-based on iOS.
So I'm talking only about iOS. When I said it's Safari-based, I meant Webkit based, but I thought Firefox/Chrome actually pull parts of Safari on iOS. Quick research says that's wrong and they just use Webkit. Not an iOS dev, so someone can point out better sources for the 100% correct terminology.
"The gigabit has the unit symbol Gbit or Gb."
25GB/s would translate to 200Gbit/s and also 200Gb/s.
I just had 25Gb/s internet installed (https://www.init7.net/en/internet/fiber7/), and at those speeds Chrome and Firefox (which is Chrome-based) pretty much die when using speedtest.net at around 10-12Gbps.
The symptoms are that the whole tab freezes, and the shown speed drops from those 10-12Gbps to <1Gbps and the page starts updating itself only every second or so.
IIRC Chrome-based browsers use some form of IPC with a separate networking process, which actually handles networking, I wonder if this might be the case that the local speed limit for socketpair/pipe under Linux was reached and that's why I'm seeing this.