4 ms·

I think you're thinking of entities like "Apple" where it is more useful to think of "the people working on WebKit at Apple". WebKit is what they do, all day,

I think you're thinking of entities like "Apple" where it is more useful to think of "the people working on WebKit at Apple". WebKit is what they do, all day, every day. They love the web, that's why they chose to go get a job working on it. To say that the people working on WebKit don't want the web to succeed as an app platform is not something I have ever seen. Go hang out in #webkit on IRC and see what you think. Edit: oh, right, so what IS going on? Exactly what it looks like: once you ship API, as Tab says, it DOES become very difficult to change due to compatibility requirements. That's why you do API review. People are saying, "why are you strong-arming this through?" It's not malicious. I do also have sympathy for Tab. Progress on the web has a committee model, and committees suck. I don't know how they ever get anything done. Maybe it would be better if everything just fragmented, at least it'd move faster.

fidotron 13y ago
Actions speak louder than words though. Apple already have integrated and deployed the Adobe CSS regions stuff, Google say it's just not their priority this year and would have performance implications on mobile. This is the weasel way to say they don't care, much as Apple are here. The devs may feel otherwise, but they are beholden to their managers who will be well aware of the strategic implications of their work. Google see Chrome as the best way to bust the iOS App Store, and as such Apple will mysteriously make the e-books in WebKit vision more compelling in the near future than the in browser app development one. I'm not saying I agree with Google here (though more for tech reasons), just that we need to be clear that the web is experiencing a schism, and that there are certain subjects which it is hopeless to expect agreement on. This is one of them.
- kenferry 13y ago
  Are you arguing that if you care about native app platforms you aren't interested in stuff like the Adobe CSS regions stuff? One of the biggest changes to Cocoa in iOS 7 was TextKit. https://developer.apple.com/Library/ios/documentation/StringsTextFonts/Conceptual/TextAndWebiPhoneOS/CustomTextProcessing/CustomTextProcessing.html https://developer.apple.com/Library/ios/documentation/String... This is concerned with the same sorts of things as regions (though it's more than that), and developers really, really wanted it.
  - fidotron 13y ago
    I'm arguing that different browsers mysteriously prioritise feature development to be in line with the strategic objectives of the larger organisations that they are in, and that this inevitably leads to conflict where those objectives are directly opposed.
- youngtaff 13y ago
  Yeh, but Apple are just as guilty of ramming things into the web platform. Take srcset for example the value it adds as a responsive image solution is up for debate but there's no hope of Apple dropping it in favour of something else - this is pretty clear from various email lists, F2F meetings (to the extent that Chrome felt they've got no option but to support it)
thrownaway2424 13y ago
What do you think Chrome people at Google do all day? Cold-call ads leads?

fidotron 13y ago

Actions speak louder than words though. Apple already have integrated and deployed the Adobe CSS regions stuff, Google say it's just not their priority this year and would have performance implications on mobile. This is the weasel way to say they don't care, much as Apple are here. The devs may feel otherwise, but they are beholden to their managers who will be well aware of the strategic implications of their work. Google see Chrome as the best way to bust the iOS App Store, and as such Apple will mysteriously make the e-books in WebKit vision more compelling in the near future than the in browser app development one. I'm not saying I agree with Google here (though more for tech reasons), just that we need to be clear that the web is experiencing a schism, and that there are certain subjects which it is hopeless to expect agreement on. This is one of them.

kenferry 13y ago
Are you arguing that if you care about native app platforms you aren't interested in stuff like the Adobe CSS regions stuff? One of the biggest changes to Cocoa in iOS 7 was TextKit. https://developer.apple.com/Library/ios/documentation/StringsTextFonts/Conceptual/TextAndWebiPhoneOS/CustomTextProcessing/CustomTextProcessing.html https://developer.apple.com/Library/ios/documentation/String... This is concerned with the same sorts of things as regions (though it's more than that), and developers really, really wanted it.
- fidotron 13y ago
  I'm arguing that different browsers mysteriously prioritise feature development to be in line with the strategic objectives of the larger organisations that they are in, and that this inevitably leads to conflict where those objectives are directly opposed.
youngtaff 13y ago
Yeh, but Apple are just as guilty of ramming things into the web platform. Take srcset for example the value it adds as a responsive image solution is up for debate but there's no hope of Apple dropping it in favour of something else - this is pretty clear from various email lists, F2F meetings (to the extent that Chrome felt they've got no option but to support it)

thrownaway2424 13y ago

What do you think Chrome people at Google do all day? Cold-call ads leads?