3 ms·
I have built a chrome app[1] that uses the webkitdirectory feature of chrome. No performance issues whatsoever. Also, we have never received a single complaint
by ryanackley 11y ago
I have built a chrome app[1] that uses the webkitdirectory feature of chrome. No performance issues whatsoever. Also, we have never received a single complaint from our 500k users about its performance.
It would make life easier for developers if Mozilla took an iterative approach. Implement it the Chrome way, then work with Google and Microsoft to implement a new standard.
[1] https://chrome.google.com/webstore/detail/readium/fepbnnnkkadjhjahcafoaglimekefifl?hl=en https://chrome.google.com/webstore/detail/readium/fepbnnnkka...
- ape4 11y agoI doubt they are inventing a problem just for fun.
- ryanackley 11y agoHave you ever worked on an engineering team?
- jfoster 11y agoFrom the article, it sounds to me as though the webkitdirectory performance issue would only become a problem with excessively large trees of directories & files. So, as you mention, in 99% (or more!) of cases it won't be a problem. Should they go with it, then? I don't know. Ultimately, I think, as you suggest, just getting something common to all major browsers that mostly works is more important than getting this absolutely perfect. Unfortunately, that doesn't seem to be what any of the browser vendors are aiming for.
- deleted 11y ago[deleted]
- rrrx3 11y agoIt's unfortunate, but this is typical behavior. I really wish it would stop, though.
- deleted 11y ago[deleted]
- startling 11y agoHistorically the iterative approach has led to incomplete, buggy, and vulnerable features that become de facto browser standards because of wide adoption.