Our great sponsors
-
file-system-access
Expose the file system on the user’s device, so Web apps can interoperate with the user’s native applications.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
That's why I wrote this: "in true Google fashion Chrome team implemented and released at least three different APIs all having something to do with files." :)
I didn't want to dig through all of them on mobile when I was responding.
Both Safari and Mozilla are open (and implement/have implemented) to Origin Private File System. Because it gives web sites an access to a file system without a chance of escaping and damaging user data. Can't remember which spec introduced it, and it doesn't really matter at this point.
For the more general part of File System Access Mozilla's and Safari's positions are: nope. https://github.com/mozilla/standards-positions/issues/154
There was also Storage Foundation API but it was thankfully never shipped (it was like a third way of handling files or something),and also received negative responses: https://chromestatus.com/feature/5670244905385984
Where file handling is concerned, there are at least
- File System Access API, https://wicg.github.io/file-system-access/
- File Handling, https://github.com/WICG/file-handling/blob/master/explainer....
- Origin Private File System, 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 This one never saw the light of day.
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/
> - 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.
Ironically I was just about to drop in absurd-sql [1] to a project, which uses indexeddb to back SQLite. This seems better.
[1] https://github.com/jlongster/absurd-sql
I haven't maintained a Vim config in a few years now (more of an Emacs man now), but I do remember using Goyo in college. Looking back at it, I think it might scratch your itch as far as Vim plugins go, it even allows you to resize the area on the fly.
https://github.com/junegunn/goyo.vim
I literally provided just some of the examples. Those are easily verifiable.
Web Transport is shipped by default. What was the input from other browser?
Here's the timeline for HID: https://github.com/mozilla/standards-positions/issues/459#is...
Constructible Stylesheets: the spec contained a trivially reproducible race condition, the API was badly specified. Google shipped against any objections and refused to bring it back under the flag. Full discussion here: https://github.com/WICG/construct-stylesheets/issues/45. Shipped in Chrome https://github.com/WICG/construct-stylesheets/issues/45#issu... (may be hidden on mobile) despite multiple unresolved issues. Two years later Chrome did add a better API that people originally requested, other issues potentially remain.
Where file handling is concerned, there are at least
- File System Access API, https://wicg.github.io/file-system-access/
- File Handling, https://github.com/WICG/file-handling/blob/master/explainer....
- Origin Private File System, 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 This one never saw the light of day.