logoalt Hacker News

Fiveplusyesterday at 2:51 PM12 repliesview on HN

This is a healthy thing to happen to the Linux browser ecosystem imho.

We talk a lot about browser diversity, but on Linux and Windows, it is a lie. You have firefox (gecko) and fifty flavors of chromium. Webkit on Linux has essentially been relegated to embedded devices or the GNOME epiphany browser, which I'll admit while is a noble effort, lags a bit in the stability and power-user features department. Big reason for that is that it lacks the commercial backing to keep up with the modern web standards rat race.

Kagi bringing orion to Linux changes the calculus. It introduces a third commercially incentivized, consumer-grade engine to the platform. Even if you never use orion, you want this to succeed because it forces WebKitGTK upstream to get better, which benefits the entire open source ecosystem.

The sticking point like always will be media playback (read: DRM/widevine). That is the graveyard where Linux browsers go to die. If Kagi can legally and technically solve the widevine integration on a non-standard Linux webkit build, they win. If not, it will be a secondary browser.


Replies

mikae1yesterday at 3:26 PM

> Webkit on Linux has essentially been relegated to embedded devices or the GNOME epiphany browser

Don't forget about https://falkon.org. It's a browser I enjoy using. WebExtension support will be big if it lands in Orion though.

EDIT: apparently Orion is not open source. Not particularly interested in a closed source browser, TBH. In 2022 they said they plan to open source "when there is merit"[1], whatever that means. No merit yet, it seems.

[1] https://orionfeedback.org/d/3882-open-source-the-browser/2

show 5 replies
justinclifttoday at 9:01 AM

> The sticking point like always will be media playback (read: DRM/widevine). That is the graveyard where Linux browsers go to die.

The Orion Alpha is happily playing back Youtube video's at 4k for me out of the box.

Confirmed it just now with this one to make sure: https://www.youtube.com/watch?v=mFG3Ah-zf18

jwcooperyesterday at 3:08 PM

> The sticking point like always will be media playback (read: DRM/widevine). That is the graveyard where Linux browsers go to die. If Kagi can legally and technically solve the widevine integration on a non-standard Linux webkit build, they win. If not, it will be a secondary browser for documentation reading only.

I'm hopeful that some day Linux will have enough users where the media companies can't ignore them. Hopefully, that day is sooner than later.

It's pretty frustrating that peacock (and all xfinity streaming) doesn't work and you can't get 1080p or 4k on most other streaming platforms.

show 6 replies
JohnFenyesterday at 2:57 PM

> The sticking point like always will be media playback (read: DRM/widevine).

Probably true in general. But for me, that's not a sticking point at all. I don't care if a browser supports media playback or not.

What I do care about is the ability to enable/disable embedded code execution (JS, at the very least) at a fairly granular level. Does Orion allow for that?

show 3 replies
forgotpwd16yesterday at 4:54 PM

The actual important part is consumer-grade. Because WebKitGTK itself is already commercially incentivized, developed primarily by Igalia (a quite underrated firm regarding their contributions in open source) who are offering consulting services mainly in embedded-related industries.

pmontrayesterday at 3:14 PM

> "DRM/widevine [...] is the graveyard where Linux browsers go to die"

Maybe it's not widevine L1 but Firefox has the widevine plugin enabled on my Debian 13. I don't remember I had to do anything except downloading Firefox from Mozilla and installing it.

https://support.mozilla.org/en-US/kb/enable-drm

Apparently it's part of Brave too but it's disabled by default

https://support.brave.app/hc/en-us/articles/360023851591-How...

I expect it to be available on Chrome and I don't expect much from Epiphany.

charcircuittoday at 4:22 AM

Browser engine diversity doesn't matter. The only important browser diversity is in the browser itself. Multiple browser engines makes it harder for developers of websites due to divergence of the engines and it makes it harder on engine developers since there are less resources going to the same engine.

isodevtoday at 4:56 AM

> commercially incentivized

So corp stuff but with devrel?

I wouldn’t install a close source browser by a ad-incentivised company like Kagi.

show 1 reply
WhyNotHugoyesterday at 6:54 PM

> The sticking point like always will be media playback (read: DRM/widevine). That is the graveyard where Linux browsers go to die.

On Firefox, you can disable DRM in about:config. Forks such as Librewolf and Tor Browser disable DRM by default.

TacticalCoderyesterday at 3:17 PM

I don't disagree with you about a new browser being a good thing but ...

> If not, it will be a secondary browser for documentation reading only.

I don't even have sound on my main desktop PC: the one I use the most. The one I do all my "life admin" stuff from (banking, real estate, etc.), all my work emails, all my coding. I think sound works but I haven't bothered to plug in speakers to check (since three years, when I assembled the PC).

That's a bit more than documentation reading.

There are work environments where even just a sound emitted by a PC is frowned upon.

People who aren't into media consumption are not just "reading documentation".

show 1 reply
satvikpendemyesterday at 6:46 PM

And Ladybird.

knowitnone3yesterday at 3:08 PM

I have to disagree with some of your points. No shade at Orin but WebKitGTK is a volunteer project. Having competition won't push WebKitGTK any faster because I am sure they are going as fast as they can. WebKitGTK already have a good list of features to add because they have other commercial browsers to compare themselves to, it's the speed that they can add them due to resource limitations. BTW, Firefox also runs on Linux. Also, nobody is installing a secondary browser for documentation reading only - what's the point of doing this?