I think this is an unpopular opinion but, I actually like that Safari is the only browser on the platform. Especially on mobile I think it's very beneficial to only have one browser for the upcoming PWA world we're trying to make. However. I only think it's a good idea, provided they (the platform devs [not just Apple]) make the browser good and up to date with current technologies. IMO there are too many edge cases in behavior with "downloading" web apps and deciding under the hood how they should be run, or even worse having behavior that causes a very annoying UX.
To clarify, I was more talking about WebKit than particularly Safari. To go on a bit of a tangent and take the current goal of PWAs and The Extensible Web to one natural conclusion is to almost completely get rid of the need of "native" applications. In this world, when a company, say Apple, wants to introduce a new platform on top of the ecosystem they've already created with iOS and macOS, such as tvOS, the idea is that they (Apple) would make the TV, put WebKit on it, and then all their users would have access to all the great web apps we know and love. At the same time I only agree with this idea in a world where (whatever company) makes the browser good (supports Web App Manifest, Service Worker, HTML5+, etc) and that a lack in engineering to bring these features to said engine would cause users to be able to switch.
Hardware is already approaching a point where it's easily faster than we are, and you almost have to try and make something non-performant. So my idea with that sentiment is that eventually all you would be buying is presentation in which case (my big jump) don't like the browser, buy something else.
Hope this helped clarify a bit :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think this is an unpopular opinion but, I actually like that Safari is the only browser on the platform. Especially on mobile I think it's very beneficial to only have one browser for the upcoming PWA world we're trying to make. However. I only think it's a good idea, provided they (the platform devs [not just Apple]) make the browser good and up to date with current technologies. IMO there are too many edge cases in behavior with "downloading" web apps and deciding under the hood how they should be run, or even worse having behavior that causes a very annoying UX.
You think it's great there is no competition? Wow ok.
So you would love there to be only Explorer on Windows?
Only Samsung Browser on my Galaxy ?
I can't wrap my head around what you're saying other than it's insane.
On Windows, no. On your Galaxy, perhaps.
To clarify, I was more talking about WebKit than particularly Safari. To go on a bit of a tangent and take the current goal of PWAs and The Extensible Web to one natural conclusion is to almost completely get rid of the need of "native" applications. In this world, when a company, say Apple, wants to introduce a new platform on top of the ecosystem they've already created with iOS and macOS, such as tvOS, the idea is that they (Apple) would make the TV, put WebKit on it, and then all their users would have access to all the great web apps we know and love. At the same time I only agree with this idea in a world where (whatever company) makes the browser good (supports Web App Manifest, Service Worker, HTML5+, etc) and that a lack in engineering to bring these features to said engine would cause users to be able to switch.
Hardware is already approaching a point where it's easily faster than we are, and you almost have to try and make something non-performant. So my idea with that sentiment is that eventually all you would be buying is presentation in which case (my big jump) don't like the browser, buy something else.
Hope this helped clarify a bit :)