paulrouget

It split. The counter part is antimatter. And there’s more matter than antimatter.

So it’s a similar question. Where does this asymmetry come from.

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.

Lot of people were saying that back then.

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 :)

Hey :) I see you guys everywhere nowadays. Congrats, and happy to see you keep on doing amazing things!

I think it's some sort of a reference to the CMB.

And it's so simple. Very easy to fork and tweak the hell out of. I added a better fonts, a 3rd swipe gesture (from top) and some random little tweaks.

Because I want my phone to be as basic as possible. No notifications, no icons, just plain text menu.

Android can be configured to be so bare that my phone is just a black screen with 5 menu items: music, signal, map, text, phone.

Personal preference.

Correct.

I need a small phone that just do basic stuff. But sadly Signal and Spotify are what I consider basic.

I tried for years to use these type of phones.

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.

We didn't.

I have a very difficult time parsing your words. I'm sorry.

I'm just saying gecko was not embeddable and was never designed to be so. There has been some efforts, and all failed.

As far as I know! … so I'd be happy to be corrected, I'd love to hear more about the history of gecko.

And you seem to know things I don't know, so I'm just asking what you are referring to. Out of curiosity.

> Gecko had, by the time that Servo was conceived, undergone refactoring that knowingly made it more difficult to embed

What kind of refactoring are you talking about?

And back to your original statement:

> Gecko was originally conceived to be embeddable by design

What are you talking about here?