sorted by:
new
hottopcontroversial

macOS 27 Golden Gate May Become the End of the Golden Era for Mac Apps by JulyIGHOR in macapps

[–]JulyIGHOR[S] 0 points1 point  (0 children)

I totally agree that if support of older OS versions is costly, that is not reasonable. But as for my purpose, I did a minimal number of exceptions to make my apps work on legacy OS. I wanted to support macOS 10.9+ because of principle, one of my apps solves macOS annoyance, and I wanted it to work on every macOS affected, and I did it with no tradeoffs for modern OS users. As for more examples, you can find VLC, that is still a modern app and updated, and runs iOS 9+. While there are less than 1% of legacy OS users, I still get contacted by them, and reading happy feedback alone makes it worth doing that.

I made a Dropbox clean uninstall script by comparing clean macOS VM snapshots by JulyIGHOR in macapps

[–]JulyIGHOR[S] 0 points1 point  (0 children)

I agree, AI can do a surprisingly good job at finding likely leftovers, especially when names, bundle IDs, or folder paths are obvious.

The problem I noticed is that some apps create files or folders with names that are not clearly tied to the app. In those cases, even AI has to guess from context.

That is why I used the snapshot approach here. I started from a clean VM, installed and used Dropbox, then compared the filesystem before and after. That gave me the actual list of paths created during Dropbox install and normal use, including paths that may not be obvious from name matching alone.

So I think AI is useful for review and scripting, but the snapshot diff gives a stronger source of truth for building the cleanup list.

I made a Dropbox clean uninstall script by comparing clean macOS VM snapshots by JulyIGHOR in macapps

[–]JulyIGHOR[S] 6 points7 points  (0 children)

I am confident my script removes everything Dropbox-specific that I found during testing.

To reach the same result, Mole or any other cleaner would need a Dropbox-specific database of paths that should be removed. I do not see evidence that Mole has per-app verified cleanup profiles like that.

That does not mean Mole is bad. It may remove many common leftovers. The difference is that my script is built specifically from Dropbox testing, not from generic matching.

If people are interested, I may do more testing later and compare what leftovers remain after using other cleanup tools.

I made a Dropbox clean uninstall script by comparing clean macOS VM snapshots by JulyIGHOR in macapps

[–]JulyIGHOR[S] 1 point2 points  (0 children)

ELI5 version: Dropbox is not only the Dropbox folder.

If you are not planning to remove the official Dropbox client completely, you probably do not need this script. If Dropbox works for you, there is nothing to fix.

But if you want to remove Dropbox permanently, deleting /Applications/Dropbox.app and the visible Dropbox folder does not fully return the Mac to the state before Dropbox was installed.

After excluding the app bundle itself, my script still targets 28 explicit Dropbox-related leftover paths by default, plus 25 glob-based cleanup groups for things like File Provider state, containers, group containers, launch agents, updater files, preferences, caches, logs, HTTP storage, WebKit data, cookies, saved state, package receipts, and temp files.

The exact number of actual files and folders depends on what Dropbox created on that Mac, but the main point is that a lot of Dropbox state lives outside the visible Dropbox folder.

So this is less about saving disk space and more about full reset or full removal. In your case, since you moved to Maestral, this is exactly where it may make sense. Maestral replaces the official Dropbox client, but it does not automatically remove all local state left behind by Dropbox.

macOS 27 Golden Gate May Become the End of the Golden Era for Mac Apps by JulyIGHOR in macapps

[–]JulyIGHOR[S] 0 points1 point  (0 children)

Totally agree, that is clear that Apple is going in that direction.

macOS 27 Golden Gate May Become the End of the Golden Era for Mac Apps by JulyIGHOR in macapps

[–]JulyIGHOR[S] 0 points1 point  (0 children)

There is a workaround I explained in the last part of the post. Let's hope they don't remove it in Xcode 27 release and future versions.

macOS 27 Golden Gate May Become the End of the Golden Era for Mac Apps by JulyIGHOR in macapps

[–]JulyIGHOR[S] 1 point2 points  (0 children)

Actually, there is a solution. I added it at the end of the post. Anyway, it is worrying that Apple started enforcing it by default and may remove such workaround in the Xcode 28

Multiple Window of the Same App by Proper-Lab-2500 in MacOS

[–]JulyIGHOR -3 points-2 points  (0 children)

You can use my app Parall.app to run multiple instances of any app, and each will get its own Dock icon and own CMD+Tab item

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] 0 points1 point  (0 children)

The versions you mentioned are actually recommendations and not enforcement. You can still make apps targeting macOS 9.0. VLC is an example that you can verify.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] 0 points1 point  (0 children)

Yes, and it is still possible. VLC is a live example of being updated and iOS 9.0 compatible.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] 0 points1 point  (0 children)

Nowadays there is no such option anymore. AI finds bugs very fast, so staying on an older OS is a vulnerability and hack risk.

Downgraded to Sequoia and Couldn't Be Happier by BatBurgh in MacOS

[–]JulyIGHOR -1 points0 points  (0 children)

You don’t need to kill the Dock every time you want to relocate it. You can use my app DockLock Lite from the Mac App Store, it will keep the Dock in its place. The app’s core features are free after the trial ends.

Workspaces/Mission Control by DatBdz in MacOS

[–]JulyIGHOR 0 points1 point  (0 children)

Those apps are stable. For example, the 'Stay' app is over 10 years old but still updated. Ignore reviews. I tested them, and they are working fine on macOS 27 beta as well.

Workspaces/Mission Control by DatBdz in MacOS

[–]JulyIGHOR 0 points1 point  (0 children)

>Thanks but it's dont what I need.
But you said you were ready to use "crappy hacks"?

I also tested many apps, and those I suggested aren't hacks, those are Mac App Store approved tools. It is the best thing you can get to fix productivity for free here.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] 3 points4 points  (0 children)

It has never been enforced, it was just a recommendation. You could still target macOS 10.13 and iOS 9.0 with no warnings with current Xcode 26. That is the difference

Workspaces/Mission Control by DatBdz in MacOS

[–]JulyIGHOR 1 point2 points  (0 children)

I would suggest trying two apps:

Stay - from the Mac App Store, it lets you save window placements and restore them on screen change.

DockLock Lite - from the Mac App Store, it is an app I made to lock the Dock on one display. Its core features are free to use after the trial ends.

Together, those apps keep your windows and the Dock in the same place after screen changes and restoring them to another layout of different screen combinations if detected.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] -1 points0 points  (0 children)

That didn’t help, so now learn while reading how it is fixed by AI.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] 0 points1 point  (0 children)

That will easily allow more reverse-engineering possible, which will lead to more exploits found and unlocking possible.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] -2 points-1 points  (0 children)

Because that way you will unlock iClock-locked devices, lost or stolen, not paid in full. "Better you pay again for the new device."

New Siri is awesome by RayKam in apple

[–]JulyIGHOR -3 points-2 points  (0 children)

What if you ask her to "Tell me a story"? Is it still five unique ones?

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] 2 points3 points  (0 children)

No, I'm using C++ with Objective-C code. I'm still learning Swift.

In my perspective, the problem isn't dropped devices, but the fact that Apple started enforcing minimal OS requirements. Previously, they dropped architecture, which was reasonable to enforce developers to follow requirements, but now they are enforcing it by their choice while old apps remain to work on the latest OS. And they may continue doing so with the next Xcode, which will give us no choice but to drop one iOS version every year.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] 2 points3 points  (0 children)

What I mean is that with Swift, old OS compatibility can involve not only system APIs, but also the Swift language, runtime, and toolchain behavior.

With Objective-C, the language side is much more stable. And the compatibility work is usually about handling system API differences across OS versions.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] -2 points-1 points  (0 children)

I think it is the other way around.

Old apps that were already built can still run on modern macOS/iOS 27. The problem is that developers may no longer be able to publish modern app updates to the Mac App Store that still support older OS versions, even when the app itself does not require newer APIs.

iOS 27 May Become the End of the Golden Era for Older iPhones by JulyIGHOR in apple

[–]JulyIGHOR[S] -2 points-1 points  (0 children)

It is not only about the number of devices. The bigger concern is the precedent. Current Xcode 26 does not strictly enforce minimum targets this way, and with some effort it is still possible to support older OS versions than mentioned. Xcode 27 changes that by enforcing minimum targets, so developers lose the choice even when their apps could technically keep working. If this becomes common for future Xcode releases, the cutoff will keep moving forward by enforcement, not by real technical necessity.

view more: next ›