fabrice_d

6 ms·

31.
by fabrice_d 1y ago
fwiw, I'm not imputing you any assumptions. I'm just pointing out that using wpt score as a criteria is not necessarily a good proxy for browser readiness. So I'm not sure why Apple uses that, other than... there's no ot
32.
by fabrice_d 1y ago
The wpt score is not that well balanced. Look at https://staging.wpt.fyi/results/?product=servo&product=ladyb... : out of about 2 million tests, more than half are for the "encoding" category. Good encodi
33.
by fabrice_d 1y ago
It looks like Amazon has people looking at Servo integration in GTK: https://blogs.gnome.org/nacho/2025/10/01/servo-gtk/
34.
by fabrice_d 1y ago
This is what https://c2pa.org/ is for. I think some camera vendors already have support.
35.
by fabrice_d 1y ago
It's a Rust based OS, so I expect people to try a Servo port instead!
36.
by fabrice_d 1y ago
No, because using Chromium was the only way the could stay relevant in the browser space. They were just unable to build the same product with their own stack.
37.
by fabrice_d 1y ago
The "almost" is very load bearing there... It's not remotely competitive with blink/webkit/gecko yet, be it for features support or performance.
38.
by fabrice_d 1y ago
Why do you think they moved to Chromium then? They switched because they could not support a competitive engine by themselves.
39.
by fabrice_d 1y ago
PostmarketOS seems to have decent support for the Fairphone 5: https://wiki.postmarketos.org/wiki/Fairphone_5_(fairphone-fp...
40.
by fabrice_d 1y ago
Are you sure about that? There are Android Go targets that are 32-bit to reduce memory usage, even on 64bits CPUs.
41.
by fabrice_d 1y ago
Main is described as "The most supported devices, with all the features and stability you'd expect from a regular OS." Unfortunately there was/is no device supported by postmarketOS that fits that description. You'l
42.
by fabrice_d 1y ago
at:// urls were unfortunately mis-designed as explained in https://github.com/bluesky-social/atproto-website/issues/417
43.
by fabrice_d 1y ago
Ladybird is extremely slow, it's far from being competitive at all.
44.
by fabrice_d 1y ago
Indeed, you should. I haven't found a Rust UI project that compiles to Wasm and has good ergonomics; they all seem to make the mistake of being frameworks that control the whole app lifecycle and reinvent either markup or cumbersome wa
45.
by fabrice_d 1y ago
Which meant having garbage collection working accross the WASM/JS barrier. This is now possible, but was not exactly trivial to design. It's a good thing that this was not rushed out.
46.
by fabrice_d 1y ago
It is possible to create a new foundation that works on a new browser product based on Gecko indeed. You just can't call it Firefox because of trademark ownership. It would be interesting to see how it collaborates / competes with
47.
by fabrice_d 1y ago
You are probably looking at a debug build. On Linux, a release build (cargo build -r) is ~4.3M, and down to ~3.5M once stripped. This could be reduced further with some tricks applied to the release build profile.
48.
by fabrice_d 1y ago
lol. As long as a browser with Chrome's market share ships it, it will be used. Whether it's an official standard by some criteria doesn't matter.
49.
by fabrice_d 1y ago
Yes, thanks for Heimdall! Indeed we did a lot of the initial dev on Samsung Galaxy S2 devices flashed with your tool!
50.
by fabrice_d 1y ago
Gecko is MPL licensed, and KaiOS abides by that license. The front-end part of FxOS was always under an Apache 2 license, much to the dismay of some employees, but that was forced by commercial partners to allow them to differentiate while
51.
by fabrice_d 1y ago
The Ars Technica review was for the 128MB phones (the Tarako project if you remember, shipping from the 1.3t branch). We never did a 64MB version, which was just a pipe dream from some BD folks to save a few cents of BOM costs.
52.
by fabrice_d 1y ago
Disclaimer: I was at Mozilla working on FxOS and then at KaiOS where I worked with the WhatsApp team to add some apis they needed. The problem was never technical, only business. WhatsApp was basically saying: "We'll build an app
53.
by fabrice_d 1y ago
The project started in 2011 and shipped first in 2013.
54.
by fabrice_d 1y ago
You can even remove the plural on "apps". The biggest commercial hurdle was the lack of WhatsApp support, which was a must have in many countries. Chicken and egg situation unfortunately.
55.
by fabrice_d 1y ago
I think you are wrong on both points: - low end devices were the only ones we could start from to get official support from chipset vendors and other partners (because they segment their market). And you need that to get eg. performance fix
56.
by fabrice_d 1y ago
Even for messages, you may need a TURN server depending on the NAT configuration of the clients.
57.
by fabrice_d 1y ago
How are you managing the initial ICE offer/response negotiation without a relay server?
58.
by fabrice_d 1y ago
Is it doing the ICE offer/answer exchange over websocket hosted on your server?
59.
by fabrice_d 1y ago
Yes, most of the problem with the semantic web is that you end up with having to agree on how to describe the world: what are the concepts, and how they are related. This kind of work on semantic networks has been done for a while in comput
60.
by fabrice_d 1y ago
I don't know how you can interpret "we'd really like to make sure that the patch works and that we don't break it in the future" as "lack of wanting to fix it", but you do you.

More ›