31–40 of 325 posts
Curious why they would use webkit, I checked their FAQ, but couldn't find any answer.
It also runs on iOS/iPadOS and Webkit is the only allowed engine on these platforms (outside Japan).
Wild that I can't use Kagi in Safari on iOS, where my search options are still locked down to three~four Apple-approved choices, of which at least one is just a multi-billion-dollar paid product placement. (Yes, I know about the extension that hijacks your searches to redirect them to Kagi, but how is that an acceptable state of affairs?)
Wild that I can't use Kagi in Safari on iOS, where my search options are still locked down to three~four Apple-approved choices, of which at least one is just a multi-billion-dollar paid product placement. (Yes, I know about the extension that hijacks your searches to redirect them to Kagi, but how is that an acceptable state of affairs?)
Earlier quoted context omitted.
I found WebKit to be very power efficient and it shows website just as other browser. What’s the issue ?
To some extent, Chrome* is the new IE. Not in that it's as shitty as IE ever was. But it's the dominant browser engine and folks are neglecting to test on other browser engines altogether as a result. They see "Works on Chrome" and move on to other things. I still encounter websites with rendering or performance issues on Firefox that Chrome based browsers don't have. * I meant Chrome not webkit.
Using WebKit makes this one of very few desktop browsers that aren't based on Blink (Chrome, Edge, Brave, Vivaldi, Opera, etc)
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.
It seems weird to run a closed-source browser on an open-source operating system when so many open alternatives exist—I certainly wouldn’t do it, and I’m a Kagi customer. Does Kagi plan to open-source Orion on Linux?
Even if it was open-source, I already have more than enough webkits on my Linux, I don't need another one.
It seems weird to run a closed-source browser on an open-source operating system when so many open alternatives exist—I certainly wouldn’t do it, and I’m a Kagi customer. Does Kagi plan to open-source Orion on Linux?
Jeez, downvoted for asking about context? People, calm down.
Earlier quoted context omitted.
This upsets me as well. I’ve sent Apple feedback[0] about it, I suggest others do the same. I wanted to use Safari at work, but this proved too big of a barrier. I can’t use the App Store at work, so no extensions. I was more willing to give up Safari than Kagi. [0] https://www.apple.com/feedback/safari/
Just submitted feedback as well. This is honestly what’s holding me back from buying a Kagi subscription at this point. Here is what I submitted: I’m requesting that iOS Safari allow users to set any search engine as their default, rather than limiting choices to a pre-approved list. Currently, Safari only offers Google, Bing, Yahoo, DuckDuckGo, and Ecosia, preventing users from choosing legitimate alternatives like…
I am pretty that is exactly the point for Apple.