When the original dev team moves on to other projects, the new guys just make minor tweaks and no major product changes happen. Big new feature releases do things like "we moved this tool from the edit menu to the file menu".
Sheets is cool, but, Excel and Word and Office365 are streets ahead of Workspace from an enterprise point of view. I've been a staunchly non-microsoft guy for years. When I was younger I was the guy writing it at Micro$oft or more likely Micro$shit. These days, managing multiple companies, some of which use Office and some which use Workspace I cringe when I need to deal with issues on the Workspace side. There are some things which Google does better. Generally APIs for the Office365 products are not as good as the APIs for the equivalent Sheets/Docs/etc product. I've done some fun/funky things with using Google sheets as an adhoc database. Put a "job" in a row in a Sheets sheet and a few minutes later something does your task and you can see the result in that sheet. Super easy to do with Sheets API, I've tried for years to get similar CRUD to work on Excel API and always hit roadblocks.
Office365 APIs for user management and groups and all the "AzureAD" stuff is absolutely top-notch.
Anything Google Cloud or cloud related, google wins hands down.
So many choices. No one product to rule them all.
Excel is probably one of the finest pieces of software devised. But not that part.
I mean, like I said, a lot of the complaints I have aren't really the fault of Workspaces.
We actually use the multiuser functionality of Sheets a lot but I still run into constant issues. And the fact a huge chunk of this crap does /not/ play nice with /multi-user local workstations/, in 2022, drives me bonkers.
For whatever reason, I recently got Excel and... yeah - way better.
It needs more resources not less, especially for the inbuilt fetching APIs, like Google finance
It's not perfect, but most of the time it feels like magic.
It is annoying that not all their features are available in browser, but I still prefer it over Google docs for anything other than lists.
Are you rsyncing Windows NFS to Google Drive or something? If so, why!?
> send in a report to the Japanese head office
Oh, that's why. Are you still mailing floppy disks, or did they get with the program and upgrade to fax already?
https://www.zdnet.com/article/japans-digital-minister-vows-t...
Luckily no floppies. But the Japanese are obsessed with over utilizing spreadsheets and want to create ones with VBA scripts for inter office use that require multiple users to utilize at once and they share them out via google drive. And their macros and scripts have hard coded pathing (don’t get me started) so they are hunting for the same drive letter path.
It took me a week to convince them what was happening when they first tried doing some of this. Beyond the hard coded paths they also had inline kanji and it was breaking everything on our American systems. Like excel would detect a broken and just delete the vba bin from the xlsx. It was kind of funny.
Google drive files live in their own hermetic world. There is a desktop client but it doesn't reliably sync to the local filesystem; when it does most of the files aren't actually searchable so you have to do two searches if the file you want might be on google drive. So stupid.
Different accounts are hermitically walled off as opposed to the "different parts of the filesystem" way you can handle locally.
And even if you can somehow do everything inside the google drive, well stuff shared with you can't be part of your file organization like it could with dropbox or, you know, the filesystem. If someone shares a directory with you google drive still won't let you make it a favorite much less move it in with the rest of your files. No, it just keeps falling lower and lower in "shared with me" as other stuff is shared with you. Pathetic.
I detest using web browsers to manage files honestly. I have yet to see it done well, there's usually a notable delay to descend into a subfolder. It's an awful experience really.
That sounds reasonable to be honest. If someone leaves and has not left the files editable by others in a group... what's the other safe option? Someone has to be the arbiter of the permissions and the IT seems like a good choice.
I can assure you that some asshat HR dude has dropped the “Gay Employee PII DRAFT2 Pre Final.xlsx” on his home drive or saved it to a public folder while trying to email it to his Yahoo account to work on it at home.
When the founder retires and the files did not get shared before, how exactly do you want to deal with that? (context: we're in a situation where we already know the standard handover / permission granting procedures either didn't kick in, or failed)
Now multiply that by hundreds of employees over years, add in 50 revisions and forks of documents, legal liability, etc. Yes it's a giant pile that just gets worse.
It's all tradeoffs and a problem you hit when you get older and bigger.
> rather than facilitating business units performing their work
Sure, and the team which enables business units to deal with this internally is... IT. I'm not saying they have to deal with every single document, but if they enable this, they deal with things that fall through cracks.
Both Google and Microsoft products are awesome in this space. They each have pretty serious deficiencies that may or may not be a big deal to you.
If that's the case, there's a pretty decent chance that you just have relatively novice spreadsheet skills/needs, so a basic tool will satisfy you (e.g. you're not so much evaluating your tools, but yourself). I'm not saying that's actually the case, just that "it works for me" gives very little information about the software you're using.
But there's an even more basic problem - trading documents with Excel users. Trying to round-trip anything more than a simple data-only Excel doc through Google Docs is folly, especially if you keep passing a document back and forth.
In case it wasn't obvious, I have to use both. I have multiple external vendors where emailing Excel docs back and forth is how you do business. Internally, we're Google Docs, except where we're not, mainly anything that touches Finance or Legal. But the Windows IT folks also use a lot of Excel. And, you get the idea.
In conclusion, the idea that anyone has a "solution" that is supposed to actually solve "sharing" is hilarious.
I don't think so. It says that the software satisfies the basic requirements of its target audience, and gives a hint as to who that audience is.
On the other hand, if you receive the opinion of some self-proclaimed expert, I think you're receiving less useful information. Experts are typically a small percentage of the userbase, and among experts there can be vastly different opinions depending on their specialty. Ask an Android dev to review vim, and an operating systems dev, and you'll get wildly different responses. If you ask a generalist software developer, you'll likely get less noise.
>> "it works for me" gives very little information about the software you're using.
> I don't think so. It says that the software satisfies the basic requirements of its target audience, and gives a hint as to who that audience is.
No, not really. What's the "target audience"? The GGP certainly doesn't say, and wrote a comparison that is meaningless unless you're already very familiar with the software (transforming it into a statement about the particular user), and perhaps misleading if you don't. I could say the exact same thing as him, except about MS Paint, e.g.
Yes, I get desktop Photoshop but I have never had to use any feature in it I couldn't get in MS Paint (I use MS Paint a lot outside of work).
Does that say MS Paint is a powerful program, or that I'm an amateur user? You can't really say unless you already know the programs, since I didn't say anything about the kinds of graphics work I actually do.
> Ask an Android dev to review vim, and an operating systems dev, and you'll get wildly different responses. If you ask a generalist software developer, you'll likely get less noise.
No, you won't get less noise, you'll just get different noise.
The latest release of Excel seems to be fully caught up to Sheets on collaboration features. We can save a file on Teams and then have multiple users editing simultaneously through a mix of desktop, mobile, and web clients it works really well.
Not to say they aren't delivering value, but I work in a place where many people have only used Google Sheets their whole career. They can't imagine running a finance org any other way.
On the rare occasion I have to put something into Excel for some business person, it's a dump from CSV.
This is a problem for all across time.
We started with Xero, but it couldn't handle our international books. For instance the NZ IRD mandates particular exchange rates, and weird tax regimes (looking at you, Canada!) were way beyond it.
Sheets means a server can securely update data remotely, and we can instantly share data with our accountants. It's a five minute job to build a sheet that mimics tax reporting forms, and you can do financial what-ifs without having to dump data to Excel.
I'm sure Excel power users will hate Sheets, but Sheets power users will hate Excel just as much. Oh, and let's revisit this after your SSD dies just after you'd perfected the ultimate data analysis formula.
I work in a company that has forced Workspaces upon us and it randomly is a nightmare. Tons of functionality you get in Excel is not there. It is a complete nightmare adjusting access to random files. You often end up with files and folders "owned" by a user who no longer exists and then we have to get the central IT to go fix it.
Ugh. Everything being browser based with crap desktop clients is the worst. They also want to constantly share crap via Google Drive and, unless I have missed something major, you can't run Google Drive, in Windows at least, under multiple signed in users with the same drive letter. You'll just get access denied errors. THAT makes shortcuts and all a complete fucking nightmare.
I have to often shrug when my users have issues and send in a report to the Japanese head office and hope they respond timely. I know /that/ isn't a workspaces fault, but it just compounds things.