71–80 of 169 posts
aside from the information: This website is sooo rediculously hard to browse on my smartphone (Nexus). The arrows are the only thing working to expand the information and they are really hard to open and close (with strange go backwards behaviour). Really bad website UX Apple.
Sorry infidel, you're not supposed to be reading this website on unblessed devices.
I don't understand the down votes since it's factual that you can't sign your plugins and distribute them inside Safari (AND ALSO keep them automatically updated) unless you pay Apple their anual fee. But well, fanboys will be fanboys.
Safari is a great browser and I'm sometimes surprised at how huge Chrome's mindshare among developers is. Every time I try Chrome out on my Mac I end up running screaming back to Safari. Safari doesn't choke on tons of tabs, it doesn't eat battery and memory for breakfast, it's never started autoplaying videos when I open a tab in the background, it's got support for picture in picture video which is my most used new…
And still does: http://caniuse.com
Safari is a great browser and I'm sometimes surprised at how huge Chrome's mindshare among developers is. Every time I try Chrome out on my Mac I end up running screaming back to Safari. Safari doesn't choke on tons of tabs, it doesn't eat battery and memory for breakfast, it's never started autoplaying videos when I open a tab in the background, it's got support for picture in picture video which is my most used new…
I wish they made it usable, favoring function over [their idea of ]beauty. I still can't use it because of the super-annoing "feature" that greys out tab favicons making impossible to immediately see what site is loaded in that tab if you have a lot of tabs open, and of course not showing the full address on iOS (I'm bother by the fact they think it's a good idea, but at least on macOS there's a setting to remove it)…
Like that super readable Chrome tab bar when you have lots of tabs open? http://imgur.com/a/MZ2dI
Not getting it right with 5-6 open seems hard even if you try.
Earlier quoted context omitted.
I enjoy Safari and use it for general browsing. However, as a developer, I perceive their developer program to be unfriendly with a high barrier to entry. That may be acceptable in a closed ecosystem like iOS but unacceptable in an ecosystem like the general web.
Safari's store & extensions are part of the Apple ecosystem, not the web's. Part of the trade off I suppose.
> The future of extensions development takes place in Xcode
and
> To develop without a certificate, you must tell Safari each time it is launched
These points can be trivial for someone who is or has no issue becoming a part of the Apple Developer Program. However, the red tape seems contradictory and almost hostile compared to developing extensions for Chrome and Firefox where all you need is your favorite text editor.
Earlier quoted context omitted.
Like that super readable Chrome tab bar when you have lots of tabs open? http://imgur.com/a/MZ2dI
There is no solution to that many tabs. Not getting it right with 5-6 open seems hard even if you try.
But that's just me I guess. To each is their own.
Safari is a great browser and I'm sometimes surprised at how huge Chrome's mindshare among developers is. Every time I try Chrome out on my Mac I end up running screaming back to Safari. Safari doesn't choke on tons of tabs, it doesn't eat battery and memory for breakfast, it's never started autoplaying videos when I open a tab in the background, it's got support for picture in picture video which is my most used new…
Whew. Custom Elements, Fetch, and async/await all at once? Christmas came real early in 2017...
Too bad we still have to use shims until iOS Safari catches up (hopefully this year).
