3 ms·

We've had support for WebGL internally for years. The decision to ship it was based on sufficiently improving graphics driver security. For most of webgl's exis

by om2 12y ago

We've had support for WebGL internally for years. The decision to ship it was based on sufficiently improving graphics driver security. For most of webgl's existence, Apple engineers have been editors of the spec. For IndexedDB, we originally wanted to keep pushing for WebSQL, and still believe IndexedDB is technically inferior. But we are setting aside our personal opinions in the interests of interoperability. There are other features we have shipped well before Chrome or Firefox. Everyone is first at something. Eventually the browser engines converge. That's how the browser market works.

Touche 12y ago
I know you guys are first on some things, but as I said those things generally are CSS related. I can't think of any web-app enabling current generation features that Apple engineers are editors of the spec. Not WebRTC, not Manifest, not Full Screen mode. If I'm wrong, please list these specs. I'm not questioning your abilities, just your priorities. JavaScript Promises are not webapp-enabling so that's irrelevant. Does your IndexedDB allow storing of Blobs? That's important for many classes of web apps (any that need to store large amounts of arbitrary data).
- om2 12y ago
  Would you consider Canvas, HTML5 Video, CSS Transitions and Animations, Application Cache, or WebSQL to be web-app-enabling features?[1] We were first to ship all of those. And they sure as heck aren't for documents primarily. Editing a spec is a separate question from shipping order or general engineering priority. Not sure why you are conflating the two. Sounds like moving the goalposts. I'd encourage to test IndexedDB in a WebKit nightly or in the Yosemite beta. It's still kind of buggy and not necessarily complete for final, but we'd love to hear about the key blocking issues from web developers. [1] Yes, it seems like AppCache and WebSQL are both likely to be replaced by newer technologies, but I don't think that's relevant to whether sufficient priority has been placed on the area of webapps.
  - Touche 12y ago
    I bring up editing spec because it is an indicator of priorities. Apple does edit specs, just not the type we're talking about here. As for your list of features you guys did first, that's great and I'm appreciative of the work, but those are all pretty dated at this point. We're talking about today's web, not that of 5+ years ago. Anything in the last 2 years? We can both list off a dozen from Google and Mozilla.
    - Touche 12y ago
      Arg, I really don't want to argue with someone I respect as much as I do. Agree to disagree on this one, and thanks for your work.

by om2 12y ago

Touche 12y ago

I know you guys are first on some things, but as I said those things generally are CSS related. I can't think of any web-app enabling current generation features that Apple engineers are editors of the spec. Not WebRTC, not Manifest, not Full Screen mode. If I'm wrong, please list these specs. I'm not questioning your abilities, just your priorities. JavaScript Promises are not webapp-enabling so that's irrelevant. Does your IndexedDB allow storing of Blobs? That's important for many classes of web apps (any that need to store large amounts of arbitrary data).

om2 12y ago
Would you consider Canvas, HTML5 Video, CSS Transitions and Animations, Application Cache, or WebSQL to be web-app-enabling features?[1] We were first to ship all of those. And they sure as heck aren't for documents primarily. Editing a spec is a separate question from shipping order or general engineering priority. Not sure why you are conflating the two. Sounds like moving the goalposts. I'd encourage to test IndexedDB in a WebKit nightly or in the Yosemite beta. It's still kind of buggy and not necessarily complete for final, but we'd love to hear about the key blocking issues from web developers. [1] Yes, it seems like AppCache and WebSQL are both likely to be replaced by newer technologies, but I don't think that's relevant to whether sufficient priority has been placed on the area of webapps.
- Touche 12y ago
  I bring up editing spec because it is an indicator of priorities. Apple does edit specs, just not the type we're talking about here. As for your list of features you guys did first, that's great and I'm appreciative of the work, but those are all pretty dated at this point. We're talking about today's web, not that of 5+ years ago. Anything in the last 2 years? We can both list off a dozen from Google and Mozilla.
  - Touche 12y ago
    Arg, I really don't want to argue with someone I respect as much as I do. Agree to disagree on this one, and thanks for your work.