We are excited to announce that Arch Linux is entering into a direct collaboration with Valve. Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave. By supporting work on a freelance basis for these topics, Valve enables us to work on them without being limited solely by the free time of our volunteers.
This opportunity allows us to address some of the biggest outstanding challenges we have been facing for a while. The collaboration will speed-up the progress that would otherwise take much longer for us to achieve, and will ultimately unblock us from finally pursuing some of our planned endeavors. We are incredibly grateful for Valve to make this possible and for their explicit commitment to help and support Arch Linux.
These projects will follow our usual development and consensus-building workflows. [RFCs] will be created for any wide-ranging changes. Discussions on this mailing list as well as issue, milestone and epic planning in our GitLab will provide transparency and insight into the work. We believe this collaboration will greatly benefit Arch Linux, and are looking forward to share further development on this mailing list as work progresses.
No it’s not. In fact, GNOME’s default browser uses WebKit, which is also FOSS since it was forked from the LGPL KHTML.
WebKit, or WebKit2? Last I checked, which was a year or so after WebKit was transitioned to a multi-process architecture, smaller FOSS browsers were stuck with the older single-process WebKit.
That must have changed since then, but if not, I can’t imagine a forked single-process WebKit has successfully kept up with new web features introduced since.
Both, since WebKit2 was renamed to WebKit the same year iOS Safari started using WebKit2, while WebKit1 was renamed to something something legacy. As an LGPL project, there’s no reason WebKit2 would be restricted to Apple.
And anyways, we do have proof: GNOME Web uses https://webkitgtk.org/, which has clear evidence of using WebKit 2.
That is excellent news to hear. The more usable alternatives for browser engines than Blink, the more the opportunity for people to jump ship to something better every time Google shows how little they care about the consumer (like they did with Manifest V3).