I’m doing the same - and also for the fact that I can finally turn off the lock screen’s swipe for camera that I seem to activate too often when my phone’s in my pocket
Depending on the number of plugins you have, you may not notice the difference in practice. I certainly don’t but I’m very much on the minimal side of things. This all said I’m definitely of the school of thought that plugin developers should be responsible for ensuring their plugins are lazy loaded, rather than leaving it up to the user, who is not as well placed to make the decision.
Well, it might work for individual plugins, but it can't work for when you use plugins as extensions for other plugins. How would plugin A know it has to load B (which is an extension of A) as a prerequisite for [lazy] loading itself?
Basically, only plugin manager can have a sane graph of plugins dependencies and know how to load them because that graph is in the end defined by the user (for the plugin manager) and plugins themselves have no clue what user might want.
My current plan is to basically never move on from macOS 14 and perhaps move away from macOS entirely when the time arrives that I’d be forced to upgrade (new hardware needed, etc)
When a new major version of macOS is released
macOS developers seem obsessed with quickly
releasing a new version of their apps that
will only run on the newest operating
system.
From then on any updates and bug fixes are
only available on the latest macOS
If you don't upgrade to the latest and greatest
macOS you are out of luck.
I fear the day when all new apps must target the
M* chip and everyone on the x64 side has a paperweight
This made even worse when Apple dictates when your
computer is no longer allowed to run the latest
and greatest OS¹.
On the Windows side, a majority of applications tend to
work on a wider range of operating systems.
¹ There are various ways of bypassing this and installing the latest
OS in a most unsupported manner.
> When a new major version of macOS is released macOS developers seem obsessed with quickly releasing a new version of their apps that will only run on the newest operating system.
This is encouraged by Apple to help with their planned obsolescence of old OS versions. With new macOS versions there is often a requirement to rebuild your apps with the latest version of Xcode which ships alongside it. This is because Apple changes lots of its internal APIs etc between OS versions, and only the latest version of Xcode supports those changes.
Also the App stores only allow new and update submissions for apps built with the latest SDK, which in turn must be coded on the latest version of Xcode, which itself cannot be run on older versions of macOS.
Is this all a conspiracy to keep people buying new computers and phones? I cannot say, but if I wanted to keep people bying more of my product this is how I would do it.
I'm not a macOS dev, so not talking from
direct experience, but you can select a minimum deployment target in Xcode as low as macOS 10.13, I believe. There must be a reason some devs choose not to support that.
Well he explained the "reason": Apple makes it very easy for devs to choose the option they want, less work from the point of view of devs.
All because they are constantly deprecating API/framework when in general they are just moving things around and nothing really changes.
You have to be a hardcore believer to not find issue with the behavior, it's so convenient for their business model.
Meanwhile on the Windows side you can find obscure software from the Vista era and chances are it will work without issues.
I think it's OK as long as I can keep my development tools and productivity tools.
I'm intrigued by Apple products because my working laptop is a MacBook Pro. I'm thinking about buying one for studying MacOS internals and app development, so as long as I'm not forced to update XCode, homebrew, caffeine, sublime text and a few other tools, I think it's fine.
The main reason to I switched from macOS Terminal is it lacks true colour support (Ghostty far from the only alternative that offers this, but it's quite similar to Terminal.app in the way that it feels, it's a decent native macOS experience)
