Plenty of time to wait.Įveryone here in this thread is talking about 'upgrading'. By then the software ecosystem for M1 is hopefully optimised and somewhat stabilised. The fanatics will say the same thing in WWDC and in September when they realise their 1st gen transition technology is already replaced. To Downvoters: Given one already has a Macbook, I am in no rush to purchase either last years model or to purchase another shiny new one especially if it is a first gen M1. I hope this is a joke right? Since I would rather dump that money on some cryptocurrency on April 30th, than dump it all on another beautiful expensive downgrade. I'll be dumping all my money into this new gear on April 30th. The M2 / M3 enabled Mac would be a more worthy upgrade, depending whether or not if they have addressed these issues rather than getting last years model. You still can't even use two monitors on the M1 Macbook Air simultaneously which I can already do on my older Macbook. The M1 adoption cycle was infested with hype and was somewhat a hacky process, especially for the developer software ecosystem, and it is still immature, un-optimised and still not ready. I always skip the first generation of any Apple product. > I have never been happier with a laptop than this first generation M1 MBP. Once you resolve the link, the symlink isn't part of the resulting path any more. Presuming `readlink(2)` was called to resolve the file at any point, you can't navigate back "up" from the resulting file, to find yourself back at the directory that contained the symlink. Those pseudo-symlinks are more than just symlinks - they appear as real directories (like Linux bind-mounts), which is helpful to avoid breaking legacy apps that expect to be able to find real directories at ~/Desktop and ~/Documents.īut, like a symlink, the "real" directory these pseudo-symlinks point to only exists in one place, and that place is ~/Library/Mobile Documents/. The hacky part is the fact that, while the Documents and Desktop folders are canonically nested inside the Mobile Documents folder, they're also linked from outside of it with weird pseudo-symlinks. Your Documents and Desktop folders - when iCloud Drive sync for them is enabled - are just regular folders inside that synced folder. It's equivalent to the root of any other synced-directory service - Dropbox, Google Drive, etc. ICloud Drive is not a "virtual folder" (I think you mean "shell folder"? Like the one that you see when you navigate up from / in the Finder?) iCloud Drive is a real place in your home directory (it is located at ~/Library/Mobile Documents/). The fact that there's never any indication whether something is being copied or not, and that apps that support a filetype are simply arbitrarily missing from some share sheets (but not all), makes iPadOS just a disaster for any serious work that spans multiple apps. So you think you copied a bunch of things into Books to read on the airplane. Or sometimes when you open a PDF in Books from another app it saves it to Books as a copy. The problem is some kind of combination of file type plus application - Gmail will let me share a PDF straight to Files or Books just fine. So I have to share to Acrobat, then share to Files or Books from within Acrobat. missing from the iOS share sheet, even though Acrobat is there. The thing that still bites me the most is that "Share" functionality of files continues to be broken in certain apps.įor example, I frequently need to save a PDF from my Google Drive app either to my local Files or the Books app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |