Theo the Leopard Gecko, ruler of all he can see, standing on his tiny hind legs, leaning on a log, starting out the front of his glass enclosure. Watching hoomyns in their hoomynarium. In return for his keeping us safe, we lavish him with edibles delights, clean his kingdom and generally fawn over his excellence. Even cleaning up his royal poo is a gift he keeps on giving.
#SailfishOS#Gecko dev diary Day 35. In which we experiment with partial builds, tackle graphics, update strings and generally deal with a lot of upstream refactoring.
#SailfishOS#Gecko dev diary Day 29. In which we tackle private session, forward and back refactoring. Which sounds way more dramatic than it actually is!
On a eu beaucoup de chance pendant ce #voyage car on n'a pu voir dans la nature la majorité des espèces végétales et animales listées dans notre guide de la faune & de la flore de La Réunion 💚
Ici Tristan tient un petit #Gecko ou plutôt un Phelsuma Grandis, il n'est pourtant ni indigène encore moins endémique de l'île, c'est une espèce exotique, importée et pas vraiment la bienvenue sur l'île 😅
Nous avons pu observer de loin quelques très (trop) rares specimens endémiques de l'île, le Phelsuma Borbonica, espece protégée : on ne les a même pas approché, on était juste trop content de pouvoir les regarder se balader sur des Vacoas 🖤
At the beginning of the pandemic, this little guy was hiding in my home, between the rolls of paper towels. He was a welcome guest, seeing as how we were all locked down and isolated. I'd still appreciate the occasional lizard guest
#SailfishOS#Gecko dev diary Day 17. In which we're tackling things head on. Burnout, the removal of VarCache (for preferences) and the dawning realisation that GLScreenBuffer has been completely removed!
Every time I reinstall #Firefox I'm reminded that #Mozilla deliberately fails to sync my default search engine from my other browsers. I will probably continue to use Firefox until Mozilla dies, but honestly their death can't come soon enough.
The fundamental problem with any #Gecko based browser that's not #Firefox or any #Chromium based browser that's not #Chrome (or Chromium itself) is that they're always chasing a moving target. Neither has a stable API, because neither has embedding as a primary use case; their respective browsers are their primary use case. For a security update to reach a fork, it first has to hit the open source repo, then it has to get merged into the fork, and then the fork has to be released. This means there will always be some additional delay.
This might be fine if you have other concerns besides timeliness of fixes that the fork address. But unlike many on here I don't have privacy concerns about #Mozilla. By far my biggest concern about them is their dependence on funding from #Google. My second biggest concern is that their attempts to gain independence from that funding lead to things like #Pocket and ads in the browser. Which is why I say "die" rather than "gain independence from Google". I don't like what their vision of independence looks like. It's like they learned nothing from #Netscape.