31–40 of 154 posts
No mention of PWA features (specifically manifest/installation/web push) is so lame. Classic Apple politics.
Earlier quoted context omitted.
You should understand the argument before you form an opinion on it. First of all, there are plenty of us who have legitimate use cases for web push. Second, if you care about being bothered by shitty sites prompting you unprovoked, you have a couple options: content blockers or use different sites. The need for notifications is real and Apple’s choice to exclude their availability in iOS is a business move not a tec…
> The need for notifications is real Do you keep metrics on acceptance rates? How many of the notification prompts that you pop up are actually accepted? How much of the time are you just annoying your users?
Hard to understand what each of this items mean since there is no tracking issue# mentioned. Some of items cannot even be googled, what's "Turbo DFG"?
Data Flow Graph, JavaScriptCore's optimizing JIT.
https://webkit.org/blog/3362/introducing-the-webkit-ftl-jit/
Earlier quoted context omitted.
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.
While I Personaly wouldn't drop JPEG support yet... Do non-web software developers support every CPU architecture? Because I'm sure I've heard of apps that not run on macs, or just windows and not Raspberry Pis.
Earlier quoted context omitted.
Hopefully not. I'd hate to click through "This site wants to push new ads to you. Allow notifications?" modals on my shiny new iPhone (edit: in addition to content being constrained to poststamp-sized areas between GDPR banners).
You should understand the argument before you form an opinion on it. First of all, there are plenty of us who have legitimate use cases for web push. Second, if you care about being bothered by shitty sites prompting you unprovoked, you have a couple options: content blockers or use different sites. The need for notifications is real and Apple’s choice to exclude their availability in iOS is a business move not a tec…
Such as? The only use case for notifications and PWAs I'm coming across are clickbait news sites creating a sense of urgency with "homepage was updated" modals obscuring content and capturing click events. Web user agents have freedoms in rendering pages to users, and Safari siding with users and power efficiency is a good thing. In line with other comments, I predict browsers will soon provide opt-out for notifications, then eventually deprecate them altogether, like they did with popups/popunders.
Now, more importantly, Safari could work on their odd pick list control rendering like a dial wheel.
Earlier quoted context omitted.
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.
While I Personaly wouldn't drop JPEG support yet... Do non-web software developers support every CPU architecture? Because I'm sure I've heard of apps that not run on macs, or just windows and not Raspberry Pis.
Earlier quoted context omitted.
Hopefully not. I'd hate to click through "This site wants to push new ads to you. Allow notifications?" modals on my shiny new iPhone (edit: in addition to content being constrained to poststamp-sized areas between GDPR banners).
You should understand the argument before you form an opinion on it. First of all, there are plenty of us who have legitimate use cases for web push. Second, if you care about being bothered by shitty sites prompting you unprovoked, you have a couple options: content blockers or use different sites. The need for notifications is real and Apple’s choice to exclude their availability in iOS is a business move not a tec…
No mention of PWA features (specifically manifest/installation/web push) is so lame. Classic Apple politics.
PWA is not one single thing that needs a special mention, bunch of features they have listed will account for a better cross platform web & mobile experience.
Earlier quoted context omitted.
You certainly want a good way to sort, classify, combine and remove reported bugs (which Trac also makes awful), but you should never put up barriers to accepting bug reports. My rule of thumb is that every bug that someone reports affects 9 other users who couldn't/didn't report it. (Probably with Trac it's 1:99 because of how difficult it is to use.)
If you tell people to submit bugs to a mailing list, that means that devs will manually confirm bugs before putting them onto the bug tracker: this gives an incentive to get them taken care of faster, because right as it's added, someone who knows the codebase has a general idea of what's wrong. Mail is standard, so it's not really a barrier. It kind of lessens the Caps-Lock Warriors of Bugzilla-like systems, though.
Earlier quoted context omitted.
You should understand the argument before you form an opinion on it. First of all, there are plenty of us who have legitimate use cases for web push. Second, if you care about being bothered by shitty sites prompting you unprovoked, you have a couple options: content blockers or use different sites. The need for notifications is real and Apple’s choice to exclude their availability in iOS is a business move not a tec…
> There are plenty of us who have legitimate use cases for web push Such as? The only use case for notifications and PWAs I'm coming across are clickbait news sites creating a sense of urgency with "homepage was updated" modals obscuring content and capturing click events. Web user agents have freedoms in rendering pages to users, and Safari siding with users and power efficiency is a good thing. In line with other c…
Such as a user presses a button in order to enable push notifications.