> Not that anyone cares or doesn't know, but⦠> Don't underestimate how hard a file system is to make. My wife's work > uses Google web apps but they might switch to MS's competing products > (horrors). One of the complaints is Google can't reliably store "files", > they move around and get lost. Maybe Google stores the files themselves > as blobs out in a file system, but all the metadata about the file, > including the simulated "location" that is presented to the user, is > being stored in a database. And it is hard to get that right. > (Particularly in this world of continuous integration/continuous > deployment, that worships feature velocity, is not designed before it is > built, and fired the QA department.) > > > -kb, the Kent who will shut up now.
This seems like it is a serious issue. If you could characterize this and show some examples, I can send it off to the appropriate group at google. There is no reason what so ever that google "can't reliably store "files", they move around and get lost" if you are seeing this, that is serious. _______________________________________________ Discuss mailing list [email protected] https://lists.blu.org/mailman/listinfo/discuss
