Because measurements confirm a homogeneous and isotopic universe. A spherical universe would imply a special point, the center, which would go against these cosmological principals.
That's something I was thinking a lot about back when I was working on Servo. Wasm + a protocol to talk to WebRender (expose display lists [0] to the wasm runtime). Some sort of "mini web", a minimal runtime that would do just enough that most web APIs could be re-implemented and shipped from the webpage directly. The DOM, the CSS parser, the layout engine, … could just be shipped as wasm modules.
Kind of defeat the purpose of view-source, but nowadays, it's a lost battle already.
And I didn't think too much about sandboxing, accessibility, network or whatnot. Just a fun idea…
But… the 3.6 -> 4.0 release was just such a pain. We spent more than a year trying to cram too many features in v4.
Clearly feature-based releases were just not cutting it, especially as Chrome was shipping new versions fast.
For the longest time people were saying it was the wrong move, but really - that was absolutely necessary, and proved out to be the right thing to do. The Stable / Beta / Alpha ("aurora", was that the name?) channels massively improved our yield :)
I need Signal… so it had to be an Android phone. I also need a good map app, and Spotify.
I tried many of these phones, and they all had 2 main problems: poor build quality (random shutdown, compass failing, random android bugs), and bad bluetooth, making it impossible to use headphones (I even tried to use wired headphones, but then, there's no wired earbuds with active noise cancelling).
The only phones that were "good enough" were the 4" Unihertz Pocket and the 3" Jelly.
But the bluetooth situation was unbearable (cracking noises, sync issues), and some hardware problems just made me anxious (couldn't rely on the phone to wake up, or going on a hike).
I just ended up getting a Zenfone 8, which is a massive phone, but considered the smallest. It's way too big for me, and does way too many things. But… there's no other options sadly.
Alright, you don't have to engage. I thought maybe I missed something before my time.
For others and historians :) … some efforts were made I think around 2008 (by Brad L. and/or Mark F. … I don't remember so well). A shortlived GTK widget was attempted at some point.
But this lead to nowhere because… well, it's hard to bend Gecko that way, because, again, Gecko was not designed to be embedded. And also because leadership was not pushing into that direction.
About the "not designed that way", what I mean is this:
We had many abstractions for sure to make it multi-platform (and that was amazing achievement, really) but embedding requires mechanisms to hook the event loop and the rendering pipeline into the embedder, in an agnostic way. Which is the part that was missing in Gecko.
Webkit had a proper, well designed, embedding story.
In the case of Thunderbird and seamonkey, Gecko was not embedded, but was the "embedder".
For a short time, there was some attempts (native cocoa and gtk widget) to embed gecko, but it was really not meant to be, it was really hacky and never matured.
https://www.mozilla.org/keymaster/gatekeeper/there.is.only.x...
Good old time.