5 ms·

Can you just slow down for a moment and focus on what you said? > We're literally in the discussion about File System API that is: > - not on any standards tr

Can you just slow down for a moment and focus on what you said? > We're literally in the discussion about File System API that is: > - not on any standards track As others have pointed out the standard is here: https://fs.spec.whatwg.org/ https://fs.spec.whatwg.org/ > - considered harmful by other browser vendors It is literally being drafted in conjunction by all the major browsers. > - shipped by default in Chrome So what? I for one am thankful that Chromium enables features earlier than other browsers. If you don't want the Chromium implementation then don't use it.

dmitriid 4y ago
> As others have pointed out the standard is here: As others also pointed out, it's a different standard. File System: Mozilla isn't opposed File System Access API: considered harmful There are parts (of whichever spec) that neither Mozilla nor Safari are opposed to like Private Origin File System. That one ships across all browsers. > So what? Ah yes. So what if a dominant browser ships features without any consensus, against objections, with badly written specs, or with glaring issues. As to "don't use it", https://news.ycombinator.com/item?id=31905404 https://news.ycombinator.com/item?id=31905404
- 8n4vidtmkvmk 4y ago
  wait, there's 2 different...? I don't even know what I can call them if not "standards" and only one has "API" in the name.
  - dmitriid 4y ago
    Where file handling is concerned, there are at least - File System Access API, https://wicg.github.io/file-system-access/ https://wicg.github.io/file-system-access/ - File Handling, https://github.com/WICG/file-handling/blob/master/explainer.md https://github.com/WICG/file-handling/blob/master/explainer.... - Origin Private File System, https://github.com/WICG/file-system-access/blob/main/AccessHandle.md https://github.com/WICG/file-system-access/blob/main/AccessH... There was also Storage Foundation API to which the reaction was "I don't think it's an acceptable outcome for the web platform to have that many ways to work with files" :) https://github.com/mozilla/standards-positions/issues/481 https://github.com/mozilla/standards-positions/issues/481 This one never saw the light of day.
    - 8n4vidtmkvmk 4y ago
      I don't think that's acceptable either. How hard can this be? Just make the user consent to give access and maybe up to some max disk space. Done.
      - dmitriid 4y ago
        "Just" carries a lot of weight there. There are several dozen APIs that Google pushes that require user consent. At wich point will the user just blindly click "yes" on all of those?
        8n4vidtmkvmk 4y ago
        That's a fair point. Sometimes I go the opposite extreme. If every site is asking to send me notifications, I'll turn it off globally. Sites shouldn't be asking for permissions that don't really need, and users should default to "no" instead of yes, but these are orthogonal problems. Browsers could batch them up. One dialog that lists what permissions the site wants with checkboxes next to each of them to agree. There really is no way around that for file system access. Users must consent and consent to a small subset of files, or the whole thing is effed.

dmitriid 4y ago

> As others have pointed out the standard is here: As others also pointed out, it's a different standard. File System: Mozilla isn't opposed File System Access API: considered harmful There are parts (of whichever spec) that neither Mozilla nor Safari are opposed to like Private Origin File System. That one ships across all browsers. > So what? Ah yes. So what if a dominant browser ships features without any consensus, against objections, with badly written specs, or with glaring issues. As to "don't use it", https://news.ycombinator.com/item?id=31905404 https://news.ycombinator.com/item?id=31905404

8n4vidtmkvmk 4y ago
wait, there's 2 different...? I don't even know what I can call them if not "standards" and only one has "API" in the name.
- dmitriid 4y ago
  Where file handling is concerned, there are at least - File System Access API, https://wicg.github.io/file-system-access/ https://wicg.github.io/file-system-access/ - File Handling, https://github.com/WICG/file-handling/blob/master/explainer.md https://github.com/WICG/file-handling/blob/master/explainer.... - Origin Private File System, https://github.com/WICG/file-system-access/blob/main/AccessHandle.md https://github.com/WICG/file-system-access/blob/main/AccessH... There was also Storage Foundation API to which the reaction was "I don't think it's an acceptable outcome for the web platform to have that many ways to work with files" :) https://github.com/mozilla/standards-positions/issues/481 https://github.com/mozilla/standards-positions/issues/481 This one never saw the light of day.
  - 8n4vidtmkvmk 4y ago
    I don't think that's acceptable either. How hard can this be? Just make the user consent to give access and maybe up to some max disk space. Done.
    - dmitriid 4y ago
      "Just" carries a lot of weight there. There are several dozen APIs that Google pushes that require user consent. At wich point will the user just blindly click "yes" on all of those?
      - 8n4vidtmkvmk 4y ago
        That's a fair point. Sometimes I go the opposite extreme. If every site is asking to send me notifications, I'll turn it off globally. Sites shouldn't be asking for permissions that don't really need, and users should default to "no" instead of yes, but these are orthogonal problems. Browsers could batch them up. One dialog that lists what permissions the site wants with checkboxes next to each of them to agree. There really is no way around that for file system access. Users must consent and consent to a small subset of files, or the whole thing is effed.