Technology

59589 readers

3024 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

883

Arch Linux and Valve Collaboration (lists.archlinux.org)

submitted 1 month ago by Aatube@kbin.melroy.org to c/technology@lemmy.world

211 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] pivot_root@lemmy.world 1 points 1 month ago (2 children)

like Microsoft with Apple in 1997

https://wccftech.com/microsoft-invested-150-million-in-apple-27-years-ago-today-on-august-6/

Google with Mozilla today

That's funny because this is the opposite of what you seem to be suggesting. This is not helping their competition, this is paying another company hundreds of million dollars to be anticompetitive against their competition. They paid Mozilla (and dozens of others) to be the default search engine. Its the exact anticompetitive behavior that caused them to be legally classified as a monopoly.

Google has multiple ventures: advertising, search engine, email, web browser, cloud storage, cloud infrastructure, etc.

I'm not saying they don't get any other benefit from paying Mozilla. I'm saying that one of the reasons Google shovels money in their direction is to stop regulators from having a reason to take a closer look at Chrome's dominance.

In terms of browser engines, we have: Blink (Chromium), WebKit2 (Safari), and Gecko (Firefox). WebKit2 is exclusive to Apple devices, which leaves Blink and Gecko as the only two browser engines available on Windows and Linux. If Mozilla went bankrupt and stopped developing Gecko, Google's Blink engine would have no competition on non-Apple platforms, which would invite some regulatory scrutiny.

[–] Aatube@kbin.melroy.org 2 points 1 month ago (1 children)

WebKit2 is exclusive to Apple devices

No it's not. In fact, GNOME's default browser uses WebKit, which is also FOSS since it was forked from the LGPL KHTML.

[–] pivot_root@lemmy.world 1 points 1 month ago (1 children)

In fact, GNOME's default browser uses WebKit

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.

[–] Aatube@kbin.melroy.org 2 points 1 month ago (1 children)

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.

[–] pivot_root@lemmy.world 2 points 1 month ago

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).