#SailfishOS#Gecko dev diary Day 160. Disentangling the Web Render Layer Manager from the Client Layer Manager. It turns out trying to do this while travelling by train isn't the best approach 🚂 💻 📱
In this one, we have #Mozilla switching CEOs after launching a frankly overpriced service, we have #Apple doubling down on their malicious compliance, this time breaking PWAs voluntarily, and we have Wine and DXVK coming to #Android, but closed source:
#SailfishOS#Gecko dev diary, day 150! After a two week break for #FOSDEM I'm back to daily-blogging about gecko again. Today, a bit more progress with the sessionHistory.
Also at #FOSDEM catch me in the FOSS on Mobile Devices Devroom talking about upgrading #Gecko for #SailfishOS, my experiences daily blogging about it and the great support I've received from the amazing #Sailfish#Community.
This is huge! This could allow other Web browser engines like #Firefox's #Gecko to run on iOS, and expand the possibilities with #WebAssembly on iOS, by allowing engines like #wasmtime to run in Apple phones 🥳
(o/c terms and conditions apply, and the costs might be prohibitive)
@mkiol No question. It's certainly always important to seek alternatives. However, #Brave is one of the examples (#Vivaldi, #Edge, #Chrome, #Chromium, #Bromite …), which I find also troubling because at the end of the day, it's focused on just one rendering engine. These are then monopolies, which are often not good for the user. #Mozilla's is actually the only competitor currently regarding rendering engines (#Gecko, #Quantum) to Google (#Blink. #WebKit).
#SailfishOS#Gecko dev diary Day 124. The final post of 2023 🍾 🎆 And so very nearly the final post on the printing pipeline. Today I'm working through the theory of the JavaScript changes needed to tidy everything up; tomorrow I'll implement them.
I'll be talking about my whole experience (successes and failures) upgrading the Gecko engine for Sailfish OS from ESR 78 to 91 in the cold light of day, including all the amazing help and encouragement from the community.
A lot of people seem to have opinions on browser cores.
We built one. From scratch. We know what it takes to do, also knowing that big tech does its best to create incompatibilities.
Presto was, IMHO, the best browser engine, but that was more than 10 years ago. I wish development had not been halted and it would not have been halted if I had had anything to say about it.
Now we build Vivaldi on Chromium and we do feel it was the best we could do. We can build a great browser based on Chromium. I hope you are all enjoying Vivaldi. If you have not tried it, please do.
Accidentally shifted a storage container on the patio while rummaging around in it, and started a little gecko who had been peacefully minding his own business underneath.
#SailfishOS#Gecko dev diary Day 85. It's time to start back up again! Beginning with a quick recap of what's been happening over the last two weeks 📱 🦎 🐟
The plan is to go back to daily posts again, initially looking at some smaller, quicker tasks.
I've switched from Chrome to Firefox about a decade ago. It's just as fast and intuitive, and container tabs are a game changer. It always catches me off guard when I see its market share is so low.
@Gargron
I also use Firefox because it has its own engine - #Google otherwise has a monopoly with #Chrome, while #Mozilla continues to use #Gecko. And I mean, #Firefox is very fast if it doesn't have 200 add-ons running...
Maintenant que #Firefox Desktop a corrigé sa fuite Blob, il réussit tous les tests de partitionnement d'état (fuite de données entre sites) de Privacy Tests ! Et ce correctif c’est également propagé à #LibreWolf.
Le moteur #Gecko de Firefox devient ainsi le premier des 3 principaux moteurs (Gecko, WebKit, Chromium) à avoir un bilan de santé impeccable en matière de fuites de données intersites sur ordinateur.