Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WebKit Goals for 2020

trac.webkit.org

Post reply on HN
Print view View original

101–110 of 154 posts

Re: WebKit Goals for 2020

#101

Post by royal_ts »

hqrlk wrote: post #63
joneil wrote: post #19

Earlier quoted context omitted.

Browser vendors are finally catching on. From Firefox 72 permission prompts won’t be shown unless they’re triggered from a user interaction. From the blog post: > Notification prompts are very unpopular. On Release, about 99% of notification prompts go unaccepted, with 48% being actively denied by the user. https://blog.mozilla.org/futurereleases/2019/11/04/restricti... I’ve heard Chrome is moving in a similar direct…

So instead of getting a permission prompt on load, I will get it when I first click on something. No thanks.

No. It should be done the way like Slack does it: - You want to get Notifications for Messages? Click here

So that you actually know what it's used for

Re: WebKit Goals for 2020

#102

Post by saagarjha »

SiVal wrote: post #98

Apple 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…

> start outperforming your competition instead of merely banning your competition

FWIW, Safari generally outperforms competing browsers on benchmarks.

Re: WebKit Goals for 2020

#103

Post by saagarjha »

royal_ts wrote: post #101
hqrlk wrote: post #63

Earlier quoted context omitted.

So instead of getting a permission prompt on load, I will get it when I first click on something. No thanks.

No. It should be done the way like Slack does it: - You want to get Notifications for Messages? Click here So that you actually know what it's used for

I'm dealing with a bug currently where Slack doesn't keep track of whether I've enabled notifications, so I always get the banner. I think I'd go mad if every website did that :(

Re: WebKit Goals for 2020

#104

Post by jlokier »

tmikaeld wrote: post #3

I've been implementing FIDO2 into my serverless application, finally there will be iOS support! It really is the golden authentication method, it's very thought through and incredibly easy to use (unfortunately not to implement though)

FIDO2 is working, but I wouldn't call it "golden" at all.

Tying authentication to a single device you can lose, especially one controlled by the device vendor not by yourself, sounds highly risk prone to me.

As far as I'm aware, this is not yet a solved problem with WebauthN or FIDO2 standards - they simply recommend that you provide another authentication method or backup device for recovery, and leave it to you to figure out. (If I've got this completely wrong, I'd love to know.)

Although not the same thing, in a similar vein we're already hearing about people locked out of bank accounts that were created in a phone app, and Google doc accounts that they can't log into any more.

I wouldn't make the decision to run a business on the back of serverless services I could only get into with FIDO2 keys that are hidden in a vendor device that might die any day.

For now, I'll stick with backed up SSH keys and very secret passphrases :-)

Re: WebKit Goals for 2020

#105

Post by shantly »

kmlx wrote: post #56

as is tradition already, webkit is missing: - full PWA - ServiceWorkers - VP8/9 - webvr - and many others this could all be mitigated if aapl would let us install custom non-webkit browsers on ios. unfortunately it seems we will need the courts to force aapl.

Incidentally, is there a way to disable service workers on desktop Safari? Twitter’s went rogue the other day and started eating a whole core, non-stop. I don’t want or need them. Ever. Hopefully mobile safari doesn’t let developers do that to my phone, too.

Re: WebKit Goals for 2020

#106

Post by greggman2 »

saagarjha wrote: post #102
SiVal wrote: post #98

Apple 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…

> start outperforming your competition instead of merely banning your competition FWIW, Safari generally outperforms competing browsers on benchmarks.

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

Re: WebKit Goals for 2020

#107

Post by saagarjha »

greggman2 wrote: post #106
saagarjha wrote: post #102

Earlier quoted context omitted.

> start outperforming your competition instead of merely banning your competition FWIW, Safari generally outperforms competing browsers on benchmarks.

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

Re: WebKit Goals for 2020

#108

Post by The_rationalist »

The_rationalist wrote: post #90

It'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…

Readers don't feel in accordance with my analysis. Sadly no thoughts have yet been outputed..

Re: WebKit Goals for 2020

#109

Post by maximegarcia »

asadkn wrote: post #59
newscracker wrote: post #9

Will 2020 be the year when WebKit, and the Safari browsers by extension, will have full and proper support for Service Workers and PWAs on par with other browsers? I recall reading that Safari lags behind on it, and the allegation was that Apple prefers native apps and doesn’t want web apps to be more popular.

No PWAs, no proper service workers, no native lazyload, no WebP, always lagging behind with more buggy implementation of almost everything. Can't blame people who call it the new IE6/8.

And web share target...

Re: WebKit Goals for 2020

#110

Post by izacus »

Carpetsmoker wrote: post #10
asciident wrote: post #5

No WebP? Safari is about to become out of date, and websites will stop working for it. I'm using WebP on my websites with no fallback to jpeg/png at the end of the year.

Imagine being software developer with a sense of professionalism and dealing with your customers as they are, even if it's annoying a tad bit of extra work, instead of telling them to sod off if they're using a browser you don't like.

> Imagine being software developer with a sense of professionalism and dealing with your customers as they are, even if it's annoying a tad bit of extra work, instead of telling them to sod off if they're using a browser you don't like.

Now imagine a platform where users are allowed to use a better browser which supports more image formats and saves their battery and bandwidth instead of being locked into a single closed piece of software for ever and ever.

And imagine a world where owners of that platform would understand something as historical as importance of free market competition and huge damage of DRM locked plaforms.

Post reply on HN