In response to all those complaining about no competing browsers on IOS. Why doesn't someone compile chromium for ios and then publish it using AltStore?
https://chromium.googlesource.com/chromium/src/+/master/docs...
WebKit Goals for 2020
121–130 of 154 posts
Re: WebKit Goals for 2020
#122Apple apparently hates the name "progressive web apps", so how about: "offline web apps" or "installable web apps" or just "unrestricted web apps"? I'd like those names more, too. Regardless of the name, where is WebKit's commitment to joining Google, Mozilla, Microsoft, and countless web developers in making web apps first-class apps on iOS? Apple keeps silently "considering" and "accidentally" messing up various as…
Most modern web tech is trash and a crutch for lazy developers.
There. I said it.
In a blunt way what so many other comments here have tried to say without offending anyone. Redirect your ire. :)
At best most uses of such tech prey upon users' information, naïveté, and hardware resources. At worst they are outright malicious.
I'm glad there is at least one company with the muscle to put their foot down on this shit. We'd still be stuck with fucking Flash if y'all had your way.
Instead of reinventing a wheel that doesn't travel far to begin with, major companies should be putting a better effort into write-once-run-natively-everywhere technologies.
I don't care if it's SwiftUI, XAML, Qt or whatever. Just stop forcing everyone to spend most of their software time in a half-assed VM when we have had perfectly capable operating systems for millennia.
Re: WebKit Goals for 2020
#123In response to all those complaining about no competing browsers on IOS. Why doesn't someone compile chromium for ios and then publish it using AltStore? https://chromium.googlesource.com/chromium/src/+/master/docs... https://altstore.io/
IOS requires all native code be signed so JIT wouldn't work. It would be a possibility on a jailbroken device, but someone would have to make a port.
Re: WebKit Goals for 2020
#124Apple apparently hates the name "progressive web apps", so how about: "offline web apps" or "installable web apps" or just "unrestricted web apps"? I'd like those names more, too. Regardless of the name, where is WebKit's commitment to joining Google, Mozilla, Microsoft, and countless web developers in making web apps first-class apps on iOS? Apple keeps silently "considering" and "accidentally" messing up various as…
What is this hope for healthy browser engine competition? On Android and ChromeOS, Chrome and Chromium-based browsers have more than 99% marketshare.
"Apple should allow non-WebKit browsers" is really saying "what's holding back the mobile web is that Google does not completely dominate it." Only one thing prevents that outcome today.
Re: WebKit Goals for 2020
#125Earlier quoted context omitted.
WAT? I see Safari being substantially slower on pretty much every benchmark I throw at it. Unless you:re on iOS where Apple bans competing browers
No, I'm talking about macOS. Instead of linking to webkit.org's results, I'll provide a relatively recently run by someone on Hacker News: https://news.ycombinator.com/item?id=17361888
An under-appreciated fact is that JavaScriptCore is really really fast, and often outperforms v8 on benchmarks.
Re: WebKit Goals for 2020
#126It's fascinating to see how pathetic this roadmap is. The totality (100%) of their planned features are already available on chromium. Guess what, even after that the chromium of today (not 2020) still has an order of magnitude more features, optimisations and testing. In human hours wise, comparing the number of full-time safari developers vs the number of full-time chromium (Google, Microsoft, opera, etc) developer…
> Apple should just be rational and make the same synergistic move as Microsoft: migrate to chromium. It would save them R&W (reinventing the wheel) money, and they could allocate it to true R&D, allowing the web to move forward for making the world a better place.
Chromium is a descendant of WebKit in the first place...
> With such absurd politics, I wonder how Apple survived through history.
Because users agree with them.
Re: WebKit Goals for 2020
#127What is "logged in API"?
They broke most federated auth scenarios with ITP, so there needs to be a way for auth to flow between websites in a way that allows users to consent and control it. The logged in API basically takes your auth state (to a first estimate) out of the 3rd party cookies and into the browser. The browser then understands when to reinject them. Ad networks lose tracking via 3p cookies, but you stay logged in to your accounts.
Re: WebKit Goals for 2020
#128It's fascinating to see how pathetic this roadmap is. The totality (100%) of their planned features are already available on chromium. Guess what, even after that the chromium of today (not 2020) still has an order of magnitude more features, optimisations and testing. In human hours wise, comparing the number of full-time safari developers vs the number of full-time chromium (Google, Microsoft, opera, etc) developer…
Note that the logged in API is not supported in Chrom(e|ium). That WI be a big deal when finished because it will help with user privacy without breaking things.
Re: WebKit Goals for 2020
#129Apple apparently hates the name "progressive web apps", so how about: "offline web apps" or "installable web apps" or just "unrestricted web apps"? I'd like those names more, too. Regardless of the name, where is WebKit's commitment to joining Google, Mozilla, Microsoft, and countless web developers in making web apps first-class apps on iOS? Apple keeps silently "considering" and "accidentally" messing up various as…
What is this hope for healthy browser engine competition? On Android and ChromeOS, Chrome and Chromium-based browsers have more than 99% marketshare. "Apple should allow non-WebKit browsers" is really saying "what's holding back the mobile web is that Google does not completely dominate it." Only one thing prevents that outcome today.
That's a novel argument against allowing competing browsers. Let's apply a basic check on its validity. Do you think Mozilla agrees with it?
I think you'll find the answer is "no." Not allowing competing browsers does not help the web ecosystem or the users. It helps only Apple.
Re: WebKit Goals for 2020
#130Please finally implement the date and time input times! https://caniuse.com/#feat=input-datetime
The fact that still isn't a thing proves to me that semantic HTML, non-bloated JS bundles, etc. just will never happen.