Second day of the @webkit Engines Hackfest starting with an overview of the new WPE architecture by Carlos García Campos. This is just what we need! #wpe#webkit#igalia
Interesting that the DuckDuckGo browser is based on Apple/Safari's Webkit engine and everything else is developed by DDG, not Google's Blink or Chromium. Good to have an alternative.
@AAKL@zdnet@jlwallen Yes, unfortunately all based on #WebKit , and I blame #Apple for not giving users a real choice about what browser they really want to use.
For now, to me, all iOS browsers are Safari in disguise 😢
The Vivaldi browser is finally making its way to iOS devices. The browser's arrival follows the approved route of using WebKit for rendering and applying Vivaldi's twist to the user interface. #vivaldi#browser#ios17#webkit
Nachdem ich mal wieder irgendeine News gelesen habe, dass Chrome nun also wirklich so dramatisch viel tracken würde, dass man ihn nicht nutzen sollte, habe ich die Gelegenheit genutzt und die aktuelle Safari-Version für zwei Wochen getestet. Leider komme ich damit einfach nicht klar. Zunächst finde ich partout keinen Adblocker, der in Safari das selbe leistet wie mein aktueller in Chrome. Das scheint ja auch nicht ganz ungewollt zu sein. Dann gibt es doch immer mal wieder Seiten, die mit einem Hinweis auf den Browser den Dienst verweigern (was ich für ein Armutszeugnis in der Webentwicklung halte und nicht für Safaris Schuld, aber das ist in dem Moment ja egal). Ansonsten ist natürlich sehr angenehm ins Betriebssystem integriert (was er vielleicht gar nicht sein sollte, aber naja), jedenfalls wechsle ich wieder zurück auf Chrome und ignoriere die weiteren Warnungen.
#Safari 17 changes the time stretching algorithm for audio/video from the terrible, deprecated lowQualityZeroLatency option to timeDomain (the default for apps since iOS 15). This now means that speech-based audio is much more pleasant to listen to when scaled up in a web app, and is something I've been looking for in #WebKit release notes for a while.
@Tamasg Admittedly, the role should become practically unnecessary once more browsers have support. And I am 100% onboard with explicit ARIA usage being moved onto elements to become implicit. After all, that's how we've ended up with so many web pages that follow a reasonably logical structure of header with nav, main, and footer. But the way it is hoisted up to become the primary focus in the #WebKit release notes, despite that particular browser stack being full of accessibility blockers, is a little bit obscene.
I am 100% onboard with explicit #ARIA usage being moved onto elements to become implicit. After all, that's how we've ended up with so many web pages that follow a reasonably logical structure of header with nav, main, and footer. But the way this new element is hoisted up as the primary focus in the #WebKit release notes, as though it will realistically solve any #accessibility problems when that particular browser stack is full of accessibility blockers, is a little bit obscene.
I started a small survey in the LinkedIn group "The R Project for Statistical Computing" about #RKWard. The results so far:
Turns out that 83 % don't know it and
circa 8 % use it.
There were 139 people who participated in the survey. Given that RKWard is among the oldest #rstats IDEs and GUIs [1], it is somewhat surprising. I suppose we should improve the advertising of our tool.
@schluff I tested it a while ago. #esquisse for #rstats was working. Just checked. Works for me in #Kubuntu. Haven't tried in #Debian. The #webkit version is the most likely issue indeed.
By the way, if you're doing #webdev, it's perfect time to start testing with Safari 17. The upgraded Advanced Tracking Protection will be on by default (in Private browsing, but many folks will opt to have it on for all websites) and it's brutally strict with invalid or missing CSP or those pesky "tracking links”.
Mobile is why #Mozilla#Firefox often gets ignored and Safari gets 1st-class treatment after Chrome / Blink. "Safari" (#WebKit) is what rich customers use on all #Apple mobile devices, so that's what #business & the #web design market responds to.
korrektur, nix extensions am ios firefox anscheinend.
..es ist ja wirklich nicht zu ertragen mal eben schnell was am smartphone nachzuschlagen. ein erbitterter kampf mit cookie bannern, abo bannern, newsletter bannern, autoplay videos, sonstiger müll der durch das pihole nicht abgefangen wird und dann noch die extralangen intros damit man auch möglichst viel werbung sieht... vielleicht will ja irgendwann auch nurnoch sowas wie chatgpt nutzen nur um das internet irgendwie zu ertragen
#Epiphany / #WebKitGTK / #WebKit is all fun and games until you run into a blank page loading heisenbug with Google Calendar, install 6 GB of debug packages, bypass the sandboxing, do a "thread apply all bt", see the #gdb process eat up over 18 gigabytes of RAM and you are forced to urgently shutdown Firefox to have enough RAM to be able to get the #debugging backtrace all the way to thread no1... only to be told that there's nothing suspicious shown at the end of the backtrace after all 🥲️
I posted about switching to Firefox as my "daily driver" browser as a little tiny step away from Chromium browser hegemony, and I had a ton of people in the replies suggesting I should just use Brave or Edge or Opera or Vivaldi instead.
I'm a little concerned that people don't realize just how pervasive this problem is. Every single one of those sits on top of the Chromium codebase.
Now that #WebKit, #Safari, Epiphany, etc. support this, I really hope we will see #Mozilla finish the job and flip the switch in #Firefox too, based on @krosylight's great work.
Hopefully then the #GoogleChrome team will acknowledge that yes, everybody in the #webdev industry wants this.