Hacker News Reader

Comment by iso-8859-1 | Hacker News Reader

Yes: https://github.com/WICG/native-file-system

https://wicg.github.io/native-file-system/

    Editor: 
        Marijn Kruisselbrink (Google)

As you may be painfully aware of by now, "web standards process" means next to nothing if Google gets to decide the standards anyway.

What are you complaining about exactly? That a standard was authored by someone who works on a browser? Would you prefer if standards were worked on by people with no browser development experience?

Here's the draft of the accessibility API [1]. The two editors are from Mozilla. Does this mean that the process of defining this API, gathering feedback, iterating and publishing it "means next to nothing" because folks from other organisations didn't chip in?

[1] - https://wicg.github.io/historical-a11yapi/taxonomy.html

Google should not be releasing an implementation before the "very early" spec is finalized. They aren't acting in good faith with behavior like that.

> Would you prefer if standards were worked on by people with no browser development experience?

How about someone not on the payroll of browser vendors?

Oh, and maybe manage them in an independent organisation with power to enforce decisions and not in something that looks more like a cartel than a standards body.

Reply on news.ycombinator.com