Although I no longer use Dropbox, this is exactly why I don’t immediately rush to install versions of macOS anymore. These newer releases need up to .7 before they are mature.
I believe it was a marketing decision. Microsoft finally got to windows "10" and Apple wanted to look like it was the leader in the OS market so their product became 11. Now that windows 11 has arrived there is already a MacOS 12. I would expect this to continue for the foreseeable future. It is a petty thing but it is what these companies do.It bothers me so much, I get confused all the time and have to look it up. I wish they had just dropped the 10 and went with macOS 16 instead of 11 for Big Sur. I kinda understood 11 due to the transition to arm, but we transitioned from power PC to x86 in 10.4 and it was not considered an “entirely new Mac OS” like X truly was over 9. And then they said screw it and dropped Monterey as 12. Apple makes great products, but boy do I hate how they name/number stuff ?
Huh, that's a workaround if I've ever seen one. Thanks for the info, appreciate it.I think they mentioned about the external drive part in their blog post. There is a way: https://techcommunity.microsoft.com...es-on-demand-experience-on-macos/bc-p/3066588
To Apple and Microsoft, it is.How is this supposed to be a better experience?
It doesn't - google is a decent company with competent devs... who still uses Dropbox? lolI wonder if this will affect Google Drive?
There's a long thread on the Google cloud community (with Google Drive dev responses) to the issues they're having supporting the changes in macOS 12.x. It's possible that 12.3 will help, or maybe it will make the existing Google drive issues worse. ?♂️It doesn't - google is a decent company with competent devs... who still uses Dropbox? lol
It's total s***. QuickLook (!!!!) is broken, that's how bad this thing is.It kind of depends on how well this macOS API works. In theory it sounds like a nice integration with macOS but having your files in the cloud but not really in the folders that you think they are could be a problem if the new software has issues.
Can you share that thread with us? I'm at one such thread, but it's still only 3 pages long. At this point, I no longer have any skin in the game, but morbid curiosity is getting the best of me. ?There's a long thread on the Google cloud community (with Google Drive dev responses) to the issues they're having supporting the changes in macOS 12.x. It's possible that 12.3 will help, or maybe it will make the existing Google drive issues worse. ?♂️
When your product digs its hooks so deeply into your computer that users can't upgrade their OS without fear of breaking it, you've made a bad product.
Devil's advocate's view: people buy computers to run applications, and operating systems are there to provide a stable foundation for running apps. If "minor" OS updates break major business apps like Dropbox and OneDrive, you've made a bad operating system.
Can you share that thread with us?
If Apple forces Google Drive to adopt this and messes that solution up as well, I'm gonna go mediaeval on them. I am, however, a bit optimistic; it's almost as if Google engineers knew – and cared about – just how bad the API was and, when forced to move away from the old one – which might explain why they changed their app from “Google Backup and Sync” back to “Google Drive”, but maybe that was just a happy coincidence – they just came up with their own custom thing… which I'm still not a huge fan of (those stupid “virtual connected server” links it creates on the sidebar every time it loads really nag me), but considering how the file structure still works and feels completely native, screw it. It's now my go-to solution for cloud storage, and I hope it stays that way.
The similar loss of Spotlight indexing for OneDrive and SharePoint libraries has been quite disruptive for people who had been doing full local content syncs. A significant loss of function for many Mac Monterey users!Per some more discussion in the above thread I linked, Google used to use a kernel extension which will no longer be allowed as of 12.3, so they are a little ahead of the game there. Unfortunately, their current implementation does not allow Spotlight to index files when drive is configured to "stream" files (as opposed to sync) and there doesn't appear to be an easy solution.
Yep. The only reason I wasn't raging mad when complaining to the Apple expert about this was because she was super knowledgable and nice, and really doing her absolute best to log all my real-time experiments and feedback. It's Apple OS Engineering I'm mad at, not AppleCare.The similar loss of Spotlight indexing for OneDrive and SharePoint libraries has been quite disruptive for people who had been doing full local content syncs. A significant loss of function for many Mac Monterey users!
Nothing has changed. I upgraded to Monterey in late September and my OneDrive stuff was immediately borked. As mentioned, none of the files are treated as local, even AFTER being opened. No "Mac specific" finder stuff works on them at all.Yep. The only reason I wasn't raging mad when complaining to the Apple expert about this was because she was super knowledgable and nice, and really doing her absolute best to log all my real-time experiments and feedback. It's Apple OS Engineering I'm mad at, not AppleCare.
We did reach the conclusion that the API was a complete mess (basically, the Finder isn't caching files until you open them for the first time, and not upon being downloaded, which is completely dumb) and that the feedback would be logged, and likely escalated.
It seems I wasn't the only one to notice this, because she did hint at many similar complaints. They'll likely fix this in some 12.3.x or even 12.x update, that much I'm sure of. Also, they should allow for on-the-fly file streaming, at least for smaller files and fast internet connections, even for those on-demand-only files, with a temporary cache.
I managed to hack OneDrive to work “the old way™”, even on an external drive, and I’ll be sure to post instructions here on how to do so (not right now because, y’know, it’s Christmas day and all that). Stay tuned!Nothing has changed. I upgraded to Monterey in late September and my OneDrive stuff was immediately borked. As mentioned, none of the files are treated as local, even AFTER being opened. No "Mac specific" finder stuff works on them at all.
That and other issues have been enough (with my and my university's workflow with Sharepoint) for me to move back to PC. I prefer working on Mac, but it's just a pain in the ass when we are predominantly Microsoft, and even the basic Office Suite on Mac is a sub-standard imitation of the Win version.