In my mind, Drive isn't a file sharing / storage system, but rather a document sharing / storage system. If you want to store large numbers of files, you should use Cloud Storage, which can handle that. Drive is the cloud equivalent of LAN shared folders - you know those janky NFS and SMB shares that were always a giant headache because of permissions and other nonsense? That's what Drive is trying to be.
Seems like they could do it without the jankiness, though.
If you have 100,000 source code files, art assets or something like that, you probably don't want to use Drive to manage them. The UI just isn't built for it and it doesn't scale.
I certainly joined GDrive believing it is designed as a cloud drive where I put whatever I'd like.
It definitely lives up to that. I'm always getting sent links to files I can't open.
That does seem how it operates. A lot of the UI is directed at document sharing.
That's what makes me double take when I hear about folks using it for some very creative, but not what I think of uses for Google Drive.
I really dislike Google Drive. I can’t imagine people would use it at all if not for the fact that it’s bundled, monopoly style, with the office suite and gmail.
Since Google won’t ever fix it, I’m hoping they rapidly make it so crappy some other competitor crops up.
Of course, with our luck, it’ll be some Microsoft offering.
I wish software would stop getting worse.
I didn't even know 3PC was used by google drive. Not sure what could be non cpincidental otuer than a technical reason for it given the very collaborative nature of this tool.
Suspicion of dark pattern is not proof of dark pattern.
(ETA: at Google in particular, the dark-pattern-conspiracy you're describing between two unrelated teams, in this case Drive and static storage, is hard to pull off because coordinating those teams requires documenting design, and it turns out a lot of folks working at Google are Hacker News-type personalities who will ask inconvenient questions if they come up. But what they have that we lack is observation of the larger security picture and the ways failure to, for example, 3PC-guard your static files can result in failure modes).
We did have unlimited storage, however last week they announced that's soon to change:
> A quota will soon be introduced on the amount of data that staff and students at the University can store in their Google account. This is part of a larger piece of work being carried out by the Google Workspace team in IT Services, to review the overall amount of storage being used by the University.
Makes me wonder if the timing is somehow related.
https://blog.google/outreach-initiatives/education/google-wo...
That may be how you view the product, but Google Drive absolutely is used as an enterprise cloud service by many large companies. And as a result, there are lots of applications that integrate with its API, etc., to serve those enterprise use cases.
I just wonder .... is that what Google built Drive for? / how much of that they were thinking of.
Sometimes there are random UX/UI/API limitations, but those usually get fixed relatively quickly when someone hits them, because they’re typically just some hardcoded limit someone put in a front end layer because it was ‘more than enough’ and they needed something. A bit of elbow grease to clean up that path if it seems useful, and it’s usually good again.
They sell enterprise plans, and have for years. It's definitely an intended use of their product.
https://workspace.google.com/products/drive/
It's funny to read your comment, because to me, Google Drive feels like an enterprise product that incidentally happens to provide a consumer-facing version as well, not the other way around.
But you are right, google offers enterprise grade solutions so is expected to support over a few million files per account or even per user. Maybe something changed due to hasty cost cutting measures given the sudden interest by many on the issue tracker.
Yes - I mean, sort of. It depends on what you define as the starting point for Google Drive. Like many Google products, the brand has been reorganized and reused a number of times.
If you look at Google Drive as an extension of Google Docs, which existed prior to 2012, then yes, it started off as personal use. But if you look at it as a thing that launched in 2012 (the introduction of the Google Drive brand), then it arguably belongs as part of the reorganization that involved ending G Suite and turning it into Google Apps for Work[0], which is now known as Google Workspace.
In fact, now that the consumer version of Google Drive has been reorganized into Google One, you could argue that the enterprise version of Google Drive is actually older than the consumer version!
Of course, all of these distinctions are somewhat arbitrary, because it's the same product that you've used all along, and the only thing that changes is the pricing and the marketing. But if we're talking about consumer vs. enterprise versions of a commodity product that essentially operates at enterprise-scale for consumers, that's also the only real difference.
It's actually quite funny that the same product (which has been improved slightly, but is largely identical to what it was over a decade ago) has had so many different brands attached to it, especially when you consider that some of those brands are essentially container formats that repackage the same underlying brand (e.g., Google Workspace contains Google Drive).
[0] There was actually a rebrand in between, from 2012-2015, but because Google's product names are Alphabet soup, I can't be sure of what they called it in the interim, though I'm positive it was a distinct product from before 2012.
There is general ignorance of what google does/is/isn't and how online storage works. I agree with the sentiment, but, I've seen many a thing from recipes, shopping lists to FPA/Proposals all hosted on google drive. Even people sell content that is hosted on google drive.
Drive is paid (consumer via One, business via Workspace) cloud hosting with a free consumer tier.
I work it in a fly neuroscience lab and we use it to store all our electrophysiology and video data. Each person in the lab is storing on average 5TB of data, and the lab as a whole stores 100TB.
The graphical user interface combined with unlimited storage for Google Workspaces is essentially an unbeatable deal. Researchers can upload there data easily through the interface. Any custom solution based on S3 or equivalent would take some time to teach and more time to maintain. Also, we're paying about $200 / month total to store 100TB of data in the cloud, which is hard to beat with other services.
I tried setting up a single account for the whole lab once, but we ran into the above 5M file limit, so we just have individual accounts per researcher and it's mostly fine for now.
You should expect this to go away soon. I support science researchers and our unlimited storage option is going away in the coming months. Options for purchasing space are limited, and not cheap.
I haven't heard about the google workspace enterprise unlimited storage going away anytime soon, although perhaps you know something I don't?
For professional use, I've usually seen it used as a document repository that can be shared by teams.
In both use cases, 5 million files seems like it'd be a hard limit to hit.
Like anything, people can push limits where it’s no longer productive to extend.
I see folks describe Google Drive errors / limits like this and people describe "a business critical operational system" and I wonder. Is Google Drive even supposed to do this thing?
Not pointing the finger back at them, if Google doesn't make it clear they probably should, but at least as an individual I always see Google Drive as a single user cloud light system that allows for some sharing and organizational functions... but still not an "industrial" type cloud service.