macOS Sonoma 14.4 removes critical functions from the fileproviderctl command
forums.macrumors.com
forums.macrumors.com
But Apple might forget about us and deliver broken software ONCE AGAIN
A large list of things that don't work and are not even being worked on doesn't sound enticing.
Things like HDMI, WiFi and Bluetooth don't work and are not being worked on.
focus was on m2 to get the release out because that is where almost all the users are.
As a result, I was the main one working on m3 before the new year, and got it through to Linux kernel loading (ie m1n1 works) and running macos under the hypervisor. Patches are submitted.
I also happen to be the one doing a lot of the wifi work.
Wifi and Bluetooth work fine on m3 - the chipset is the same as the m2.
It's listed as not working because there is no released Linux support yet.
And the definition of TBA is on the same page:
"TBA: Active work on this feature is not being undertaken at this time"
Suggestion: Add a new status for "Awaiting release".
If not, i'll try to get to adding it and updating when i get some more free time :)
I suspect most people would be happier with more-open hardware, even an ordinary consumer laptop intended for MS Windows. But if the barrier is that someone wants to use an Apple laptop, we can work with that.
I was just sick of Apple catering mainly to the rich consumer dicking around on Facebook and not to the more technical populace who wants to control what they own. I'm very happy to be off Apple, it really felt like a breath of fresh air and still does 3 years later.
There's a reason your iPhone/iPad defaults, every fucking time you try to save a file, to iCloud storage and the "default storage location" option was removed from preferences.
Apple is taking the "frog in the pot of boiling water" approach, slowly pushing everyone toward iCloud file storage, despite it being a dogshit service with numerous problems because the dev team are more interested in coordinating their nail color to their McLaren (I wish I was joking.)
I assume you're right about Apple removing the preference, but I just shared a photo, picked "Save to Files" and it defaulted to Cryptomator. In case it's helpful to know, you can also turn off "iCloud Drive" as a Location.
> If you don't know what it is, and don't use it - it probably won't affect you.
>
> But some people use this tool to control and work with apps that use the
> FileProvider API: such as Google Drive, OneDrive, Dropbox, ShellFish, etc.
It does make sense because OneDrive, iCloud and Google Drive are tie-in services. If you use Microsoft 365 / Apple / Android you are “forced” to use them to gain access to certain features, meaning there is no competitive pressure.
It doesn't matter if you're just syncing a bunch of small files (code, documents, images) but can make a big difference in bigger files (compressed archives, large media assets, etc.)
I don't want to pay for two file storage systems though and the 3 host limit on Dropbox is a shame. Without it they'd be all but guaranteed to lock me in and I would (gladly) start paying again in a year or so for more space.
Instead I switched to syncthing, which is great but not as nice.
A “refuse” to “upgrade” to the fileprovider version, as I don’t want stupid&slow functionality like iCloud Drive.
It is like 60gb+ of data I didn't want that getting hammered by 3 different tvs because I have a limit.
Also they're really not that interesting. I find them pretty boring to be honest and prefer Wallpaper engine by far.
Whatever goes on in the Apple MacOS meeting rooms every year lately is like, nothing that I could ever imagine in my wildest fever dream. Stage manager? Why do I still have 5 app packages "mounted" on my desktop after 3 years that I eject every few weeks and come right back? Webcam emojis with thumbs, cool. etc etc. That iphone webcam thing was cool for a week but i completely forgot about it until I wrote this.
I can think of so many goofy bugs or weird MacOS idiosyncracies that just never get mentioned that we deal with. I've had SO many Macbook Pros, I have 3 M1s in my house right now and I have like 2x the amount of white chargers than I have of actual laptops nowadays and they all act exactly the same.
When I wake up monday morning and bang on my keyboard no matter what version of OSX it is I have a 40%ish chance of it not waking up without me grabbing the laptop and opening the lid.
20 years later.
Honestly, nowadays, windows is my "chill and relax" OS. It's windows snapping is amazing. I hate developing on it though, I did it awhile with WSL2 years ago and had many frustrations, like completely breaking my wsl vm somehow.
This sounds like apps are being run directly from disk images. Make sure the apps are copied to /Applications/ or ~/Applications/ or wherever else preferred, make sure they’re all quit, unmount the disk images, trash the disk images, empty trash. They won’t come back.
There’s also a possibility that it’s automated third party updaters getting stuck and not being able to unmount the disk images from automatically downloaded updates but this seems less likely.
This isn’t like a bug that was introduced in the beta, and betas are intended to help find bugs.
This is functionality deliberately being removed, that is wildly known to break cloud storage software.
Not OP, but it means you should expect beta software to be broken and incomplete.
How would you know this isn't due to a bug introduced in the beta? Seems as likely an explanation as anything else at this point, unless you have some inside information.
A lot of things use a "plugin" organization, and if a certain plugin was missing -- say, due to bug leading to a failed compile, the tool would work fine but the functionality provided by the plugin would simply be missing. Not that I have any insight into this particular case, but just pointing out there are perfectly reasonable ways a bug could cause this.
Also, I've personally disabled features in a beta release when I knew the feature was broken and it would cause long term issues if someone tried to use the broken feature (like data corruption). So it could be deliberately removed but only temporarily.
Or maybe Apple just removed this to be dicks, IDK... But I don't think you do either, do you?
If you do have inside info, can you let us know whyx this was removed?
It would have been nice if they left a note of explanation but… Apple.
Creating Custom Instruments - WWDC 2018
https://developer.apple.com/videos/play/wwdc2018/410/
Yes, there isn't feature parity per se with DTrace, since when it was an impediment for Apple to replace some set of APIs or tooling?
That’s exactly what’s happening here. The poster found an issue, reported it to Apple, then commented on it publicly so others who depend on it could be made aware and also report it to Apple (they specifically say duplicate reports help).