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.
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)
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)
I guess if folks write JS with the idea that optimisations are needed in mind, then the chances of premature optimisations may go up along with those of the required ones
Yeah, I assumed it couldn’t be that, but it did read like that. “Copilots” is not the right term. It doesn’t match the title of the article I’m seeing.
Most things are automated; right now one of my main recurring tasks is to check in on the upstream repositories of my forks that add some minor customisations to Neovim plugins whenever I’m applying updates, to see whether I need to do any rebasing (this is generally fairly quick and is on the weekly-monthly scale)