3 ms·

I'm pretty sure your comment misunderstands the original comment, and even if it didn't, it is rather aggressive. Why are web-technologies suddenly inferior to

I'm pretty sure your comment misunderstands the original comment, and even if it didn't, it is rather aggressive. Why are web-technologies suddenly inferior to native technologies? Maybe I want my playlist to be accessible through a website from all my devices instead of having to download a native app on each device. The company saves money/releases an app that would otherwise never have existed, and I get to use a service in a consistent manner across all platforms. Oh, and web-apps are more secure because they have less permissions than a regular app. The author of the comment said web-app. That probably means a progressive web-app. This means there is an icon for the web-app on the home screen (like a normal app) and the user interacts with it, like a normal app, although in reality, everything is being handled by the browser behind the scenes. > Progressive Web Apps are installable and live on the user's home screen, without the need for an app store. They offer an immersive full screen experience with help from a web app manifest file and can even re-engage users with web push notifications. I would argue that in this case it makes sense for the progressive web app to have all the capabilities of a native app since that's what it looks like to the user. Of course, if by web-app, the author means "a tab inside Safari browser", then the behavior is logical and your comment makes sense, we wouldn't want Safari to churn through iOS battery. > That's good. I don't want garbage in the background to do anything javascript-related at all. Why is "javascript-related" garbage better or worse than native-related garbage? Arguably, "native-related" garbage is worse because it can do more to your phone than "javascript-related garbage".

saagarjha 7y ago
> The author of the comment said web-app. That probably means a progressive web-app. This means there is an icon for the web-app on the home screen (like a normal app) and the user interacts with it, like a normal app, although in reality, everything is being handled by the browser behind the scenes. Presumably the issue here is that there is no special case where a progressive web app can let the OS know that the content it's playing should count as background audio.
- roguecoder 7y ago
  But there is no case where it should be up to a web app whether its content should count as background audio. It is possible that a user should be able to flag such a situation, but native apps both have affirmative consent when downloading an application and have permissions models the user can manage, whereas the web has neither and web browsers need to assume both malicious and incompetent web devs will do terrible things with any feature they allow.
layoutIfNeeded 7y ago
Because native garbage from the AppStore is at least vetted by Apple. For example background execution permissions will be subject to extra scrutiny by the reviewers. Sorry, but I trust them more than those npm junkies saturating my pipes with adtech crap on every other corner of the web.
- kitsunesoba 7y ago
  And with the App Store, the user has a chance to get an idea of what the app in question does and can make judgment calls as to quality, trustworthiness, etc before any code is executed.
amalcon 7y ago
Web technologies are not "suddenly" inferior to native technologies. They have always been inferior in some ways, and superior in others. Letting javascript run when the browser isn't even in use would sacrifice one of the ways that web technologies are superior (nonintrusive when not in use) to make it a little less inferior in another way (ability to set up background tasks). That doesn't seem like a good tradeoff to me.

saagarjha 7y ago

> The author of the comment said web-app. That probably means a progressive web-app. This means there is an icon for the web-app on the home screen (like a normal app) and the user interacts with it, like a normal app, although in reality, everything is being handled by the browser behind the scenes. Presumably the issue here is that there is no special case where a progressive web app can let the OS know that the content it's playing should count as background audio.

roguecoder 7y ago
But there is no case where it should be up to a web app whether its content should count as background audio. It is possible that a user should be able to flag such a situation, but native apps both have affirmative consent when downloading an application and have permissions models the user can manage, whereas the web has neither and web browsers need to assume both malicious and incompetent web devs will do terrible things with any feature they allow.

layoutIfNeeded 7y ago

Because native garbage from the AppStore is at least vetted by Apple. For example background execution permissions will be subject to extra scrutiny by the reviewers. Sorry, but I trust them more than those npm junkies saturating my pipes with adtech crap on every other corner of the web.

kitsunesoba 7y ago
And with the App Store, the user has a chance to get an idea of what the app in question does and can make judgment calls as to quality, trustworthiness, etc before any code is executed.

amalcon 7y ago

Web technologies are not "suddenly" inferior to native technologies. They have always been inferior in some ways, and superior in others. Letting javascript run when the browser isn't even in use would sacrifice one of the ways that web technologies are superior (nonintrusive when not in use) to make it a little less inferior in another way (ability to set up background tasks). That doesn't seem like a good tradeoff to me.