4 ms·

As far as i can remember, they've been consistently behind on support for emerging web technologies (since the app store came out), it just doesn't seen to be i

As far as i can remember, they've been consistently behind on support for emerging web technologies (since the app store came out), it just doesn't seen to be in their business interests to keep up.

hutzlibu 10y ago
But it is something different, to not "keep up" with full priority, than to intentionally sabotage WebStandards ...
- lucideer 10y ago
  The UIWebView is an interesting example. They released significant performance advances in the iOS Safari web browser, but denied those features to developers of cross-platform apps on frameworks such as Cordova, artificially degrading the performance of Cordova apps compared to natively developed iOS apps. Both need to go through the AppStore anyway, but keeping as much dev lock-in as possible in terms of the tech used is obviously an interest here. Add to that the fact that what positive feature development there has been in Safari (e.g. the above-mentioned excellent es6 support in the Technical Preview) has very specifically excluded the addition of any of the APIs that begin to blur the web/native divide (web notifications, userMedia, service workers, &c.)
  - hutzlibu 10y ago
    But where does your example show, that they sabotage webstandards? It shows what I said before, yes they control their system and making it harder for other implemations if they want ... but his is something completely different.
  - hutzlibu 10y ago
    ... and it might be that they dont like certain standards ... but graphics is a different category.
- macawfish 10y ago
  Sabotage is a strong word, but it doesn't have to be intentionally malevolent. In psychology the word sabotage is often used to describe situations where people don't have faith in relationships (maybe because of personal hangups) and go at them half heartedly. When their relationships fizzle out, people said to "sabotage relationships" are often left feeling confused about what happened. Apple has consistently shown that their locked down platform is priority number one. I think there are people who, for better or worse, have grown wary of that and need some extra convincing if Apple wants to influence big decisions. Safari feels more and more like IE to me as the years go by. I just have a hard time taking it seriously and don't go out of my way to support it, just like Apple doesn't go out of it's way to support it when they have proprietary platforms that they can make vastly more money from. All that said, yes, Apple has pushed the envelope from time to time, and has made some major contributions to open standards, so credit where credit is due, and accountability where accountability is due.
shmerl 10y ago
Not really. What about MSE / DASH and touch events? Apple were often hindering adoption if new technologies, if they had their own locked up / patented alternatives, which they didn't want to undermine my accepting open competition.

As far as i can remember, they've been consistently behind on support for emerging web technologies (since the app store came out), it just doesn't seen to be in their business interests to keep up.

hutzlibu 10y ago

But it is something different, to not "keep up" with full priority, than to intentionally sabotage WebStandards ...

lucideer 10y ago
The UIWebView is an interesting example. They released significant performance advances in the iOS Safari web browser, but denied those features to developers of cross-platform apps on frameworks such as Cordova, artificially degrading the performance of Cordova apps compared to natively developed iOS apps. Both need to go through the AppStore anyway, but keeping as much dev lock-in as possible in terms of the tech used is obviously an interest here. Add to that the fact that what positive feature development there has been in Safari (e.g. the above-mentioned excellent es6 support in the Technical Preview) has very specifically excluded the addition of any of the APIs that begin to blur the web/native divide (web notifications, userMedia, service workers, &c.)
- hutzlibu 10y ago
  But where does your example show, that they sabotage webstandards? It shows what I said before, yes they control their system and making it harder for other implemations if they want ... but his is something completely different.
- hutzlibu 10y ago
  ... and it might be that they dont like certain standards ... but graphics is a different category.
macawfish 10y ago
Sabotage is a strong word, but it doesn't have to be intentionally malevolent. In psychology the word sabotage is often used to describe situations where people don't have faith in relationships (maybe because of personal hangups) and go at them half heartedly. When their relationships fizzle out, people said to "sabotage relationships" are often left feeling confused about what happened. Apple has consistently shown that their locked down platform is priority number one. I think there are people who, for better or worse, have grown wary of that and need some extra convincing if Apple wants to influence big decisions. Safari feels more and more like IE to me as the years go by. I just have a hard time taking it seriously and don't go out of my way to support it, just like Apple doesn't go out of it's way to support it when they have proprietary platforms that they can make vastly more money from. All that said, yes, Apple has pushed the envelope from time to time, and has made some major contributions to open standards, so credit where credit is due, and accountability where accountability is due.

shmerl 10y ago

Not really. What about MSE / DASH and touch events? Apple were often hindering adoption if new technologies, if they had their own locked up / patented alternatives, which they didn't want to undermine my accepting open competition.