I have a work provided M2 Pro with 32GB of RAM. After the Tahoe upgrade it feels like one of the sluggish PCs at the house. It is the only one that I can see the mouse teleporting sometimes when I move it fast. This is after disabling transparency in Accessibility settings mind you, it was even worse before.
Electron used to override a private function that makes the Mac OS sluggish on Tahoe, and apparently no one uses Electron apps while doing testing at Apple.
What I can say is that while the situation is much better than at Day 1, the whole Tahoe experience is not as fluid as Sequoia.
Also, it doesn't really matter to me if this was a private function or not, if this was Windows or Gnome/KDE people would blame the developers of the desktop instead.
This happens in pretty much every Electron app as far I know, and lots of Electron apps are like Spotify, VSCode or Slack are very likely to be in the Top 10 or at least Top 100 most used apps. And yes, I would expect Apple to test at least the most popular apps before releasing a new version of their OS.
> Maybe the thought is that an email from Apple to the dev saying fix your code would more compelling???
Of course not. Apple controls the SDK, they could workaround this in many different ways, for example instead of changing how this function was implemented they could introduce a new method (they're both private so it doesn't matter) and effectively ignore the old method (maybe also they could add a message for developers building their application that this method was removed). It would draw ugly borders in the affected apps but it wouldn't cause this issue at least.
> why do we think this would be a solve as the devs clearly ignored the previous message about not using a private method?
If anything the fact that devs can actually access private symbols is an issue with how Apple designed their APIs, because they could make this so annoying to do that nobody would try (for example, stripping symbols).
Also, the fact that devs need to access private symbols to do what they need to do also shows that the public API is lacking at least some features.
Another thing, if this only affected the app itself that would be fine, but this makes the whole system slow to a crawl.
So while devs share some of the blame here (and I am not saying they don't), I still think this whole situation is mostly Apple's fault.
why do we think this would be a solve as the devs clearly ignored the previous message about not using a private method?
If anything the fact that devs can actually access private symbols is an issue with how Apple designed their APIs, because they could make this so annoying to do that nobody would try (for example, stripping symbols).
Also, the fact that devs need to access private symbols to do what they need to do also shows that the public API is lacking at least some features.
Another thing, if this only affected the app itself that would be fine, but this makes the whole system slow to a crawl.
So while devs share some of the blame here (and I am not saying they don't), I still think this whole situation is mostly Apple's fault.
I think the failures here are that Apple should have tested this themselves and the Electron devs should have tested and resolved this during the beta period.
I don't think it's that clear cut. It looks like it was a workaround for a MacOS rendering bug going back to at least 2017, landed in 2019 and had no apparent downsides for six years[1].
The PR removing the private API code also included someone verifying that Apple had fixed the original bug some time in the intervening years[2].
I probably wouldn't have taken this approach personally (at the very least file the original rendering issue with Apple and note it with the code, though everyone knows the likelihood of getting a even a response on an issue like that), but it wasn't some cargo culted fix.
[1] https://github.com/electron/electron/pull/20360
[2] https://github.com/electron/electron/pull/48376#issuecomment...
Imagine now that you're a non tech savvy user, that probably doesn't update apps as often, they are probably wondering why "my laptop is so slow after updating". But like I said in other thread, maybe this is on purpose to make people upgrade.
If they stripped symbols, they’d get flak for not having good stack traces. I think it boils down to “if you’re huge, you’re never doing it right”.
Many of Apple's OS frameworks are managed code (ObjC/Swift); and in ObjC, calling across a library boundary is always done with a message-send — i.e. a dynamic-dispatch, necessarily symbol-table-based call into an entrypoint of the target library. So anything Apple did to "strip symbols" would make it impossible for them to have one of their libraries call into another of their libraries.
https://www.pcworld.com/article/2816273/how-microsofts-windo...
Sure, people in Hacker News now know that the issue is "that Electron bug", but I am sure lots of other people that are less tech savvy just kept questioning what the hell is happening and maybe even considered an upgrade. But maybe that is the whole point.
1. Apple should test every (common?) app and any change to the OS that they make that makes an app worse shouldn't be done regardless of why they wanted to make that change. 2. Even though Apple tells people not to use private APIs, if a program uses a private API anyway Apple should build a workaround into their OS instead of letting apps suffer their own repercussions. 3. Apple should test everything ahead of time and then go around telling all the app developers that there's a problem, as if those app developers are going to do anything about it.
No matter what Apple did here, their actual choices boiled down to:
1. Add workarounds for misbehaving broken apps, giving those apps no incentive to fix their issues, and forcing Apple to support those workarounds indefinitely; this also undermines their "don't use private APIs, they could break later" position. This is the kind of thing that made Windows into an unmaintainable sack of cruft.
2. Do what they did, which is change the API and let broken apps be broken to the user's detriment. Everyone blames Apple even though it's objectively not their fault.
2. Add some kind of non-workaround that caused problems for the app and not the user; e.g. have this private API rate limited or something so that the app ends up blocking in the call. Could cause problems for actual consumers of this API, and people would still blame Apple but in this case it would be more of their fault than option 2.
In the end, Apple can't spend their time fretting over what bad developers do wrong; they spend their time on their OS and software and if a developer writes bad software and causes problems then so be it.
Then the bugs could be reported to the various app developers, and they would have been able to get some notice. Many would have acted on it. Many of the top apps have dedicated Apple contacts already. Seems like a completely reasonable expectation?
But very few users seem to care about performance or polish, so why not save a few bucks and build your desktop software with some cheap JavaScript devs?
If electron didn't exist, it would be QT, or we'd only see native apps on Windows like the old days, and nothing at all on macOS and Linux (or just web apps).
It's not a tech issue but a cultural/management problem.
Personally I try to avoid Electron apps as much as possible, but it's pretty much unavoidable now. Docker Desktop, Bitwarden, 1password, slack, VSCode, dropbox, GitHub Desktop, Obsidian, Notion, Signal, Discord, etc. All the major apps are electron. Even in the Windows world Microsoft stopped making native and makes heavy use of their own version of Electron (EdgeWebView2) for their own apps. The freaking start menu is react native ffs.
The industry has lost its collective mind in favor of being able to hire cheap javascript talent
Swift itself is great and stable enoug now. I really like the language. SwiftUI though still needs work and is still missing functionality that you have to fall back on AppKit for so there's tons of bridges to embed AppKit views in your SwiftUI hierarchy (like NSTextView still relies on AppKit, as does some drag and drop functionality) so at a certain point you might as well just continue using AppKit.
To these companies, a "native app" is just "a web app with its own start-menu icon, no browser chrome, and access to OS APIs."
(In other words: if PWAs had access to all the same OS APIs that Electron does, then these companies wouldn't ship native apps at all!)
Given how high profile the impacted app are, yes it's their responsibility to test it. Even Microsoft does better there (or at least used to). Contacting electron and finding a solution would have been an easy step to take
Even if you disqualify the devs from being mad, everyone else gets to be mad.
In an ideal situation, they would have noticed the widespread use of this private function a long time ago, put a note on the bug report that it works around, and after they fixed the bug they would have reached out to electron to have them remove that access.
If you owe the bank $100 and don't pay, that's your problem: you'll get in trouble for it, and the bank isn't going to be unduly harmed.
If you owe the bank $100 million and don't pay, that's the bank's problem: the loss of that $100 million is going to hit the bank hard, whether or not they're the ones who are in the right and regardless of how much trouble you get in over it.
Likewise, if you're a small time app developer and you use a private method that gets yanked and your app breaks, that's your problem: your users are going to be pissed at you, you'll take the reputational damage, and even if your users are also pissed at the OS vendor they represent such a small group of individuals that the OS vendor isn't going to be unduly harmed by that.
If, on the other hand, you develop one of the most widely used frameworks and you use a private method that gets yanked and your app breaks, that's the OS vendor's problem: the number of people who are pissed off at them (rightly or wrongly) is now much larger and they're going to take some reputational damage over it, whether or not they're the ones who have the moral high ground and regardless of how much reputational damage you also take.
And that's exactly what we're seeing here: it doesn't matter that Electron used an API they weren't supposed to, people are pissed at Apple about this and Apple, rightly or wrongly, has to contend with that reputational damage if they don't take steps to prevent this sort of thing before it happens (like letting the developers know that private-on-paper API is going to be yanked in advance, or making it mechanically impossible for anyone outside of Apple's own code to invoke that API long before someone depends on it).
> has to contend with that reputational damage if they don't take steps to prevent this sort of thing before it happens (like letting the developers know that private-on-paper API is going to be yanked in advance, or making it mechanically impossible for anyone outside of Apple's own code to invoke that API long before someone depends on it).
Again, that is what dev builds are for. Developers had months to verify their software still works on an OS that has confirmed release date and has very high ration of users that install the latest and greatest.
That's why this quote is relevant to this situation: it's totally Electron's fault for not adequately testing their framework against Apple's latest developer builds, but Apple could have absolutely done more to minimize the chance that Electron would make a mistake like this and cause lots of folks to be mad at Apple over it.
Should Apple be required to? No. Will they still suffer reputational damage if they don't and something like this happens? Yes.
Welp
https://leb.fbi.gov/articles/featured-articles/fifty-years-o...
Apple's private API situation was also much more nuanced, back in the days if Adobe was using an API, private or not, it probably wouldn't be degraded in any way until the core applications moved forward. Current Apple might not give a damn though.
What portion of, say, Slack devs actually run a MacOS beta at work? Are they regular devs, or are they in QA/test? It seems to me like the latter is the far more appropriate team for this.
This is 100% on electron, they didn’t do their due diligence that every Mac & iOS dev goes through every summer before the next release. It’s been two decades of the same song and dance every year. There’s just no excuse.
My simple guess is that slipped QA or wasn’t escalated from Apple’s feedback.
Considering the amount of electron apps, expecting all developers and all users to update all their app (and guessing which one is Electron based) isn’t good user-experience.
Let’s say the change is needed in the OS, you’d expect transition time. Also, a good UX on OS would be to notify user this app is using some API in a way that could reduce experience. but guessing and expecting only the developer and user parties without the OS side is making less sense imho.
https://github.com/tkafka/detect-electron-apps-on-mac
About half of the apps I use regularly have been fixed. Some might never be fixed, though...
From: https://www.reddit.com/r/MacOS/comments/1nvoirl/i_made_a_scr...
Hence I am not surprised that they ignore their existence.
Or also the other way around, nobody who develops electron apps cares to test their app on macos in the beta releases (beta testing for developers was long out afaik).
Except if it was like that JIT JVM bug that caused apps to crash and was not in the beta release.
You have it the other way around. It should be, apparently no one making Electron bothered to test on the numerous developer and public betas to make sure their hacky override of undocumented APIs (which Apple explicitly says not to use) didn't break.
they ship-of-thesseus the crap out of their OS but replacing with parts that need these new hardware features that run slow on older chips due to software-only implementations.
I got the first generation iPad Pro, which is e-waste now, but I use it as a screen for my CCTV, it cannot even display the virtual keyboard without stuttering like crazy, it lags switching apps, there's a delay for everything, this thing was smooth as butter on release.
I was considering just replacing the battery and keeping it for several more years but now I feel forced to upgrade which has me considering whether I still want/need an iPad since I'd also have to buy a new magic keyboard since they redesigned it, and they bumped the price ($1299 now vs. $999 when I got the 4th gen) so I'd be looking at $1700. Trying to hold out for an iPad Air with ProMotion.
I may be in the minority here, but I think 5 years is too short of a lifespan for these devices at this point. Early days when things were advancing like crazy, sure. But now? I have 8 year old computers that are still just fine, and with the M-series chips I'd expect at least 10 years of usable life at minimum (battery not withstanding)
What in the actual world of software engineering?
The iPad Air 13 with a M3 is a really nice experience. Very fast device.
> You cannot restore to any iOS versions other than signed ones. All SHSH blobs are currently useless.
So, anything newer than iPhone X can’t be downgraded
I just got one example while passing the mouse quickly through my dock (I still use the magnify animation) and I can clearly see it dropping a few frames. This never happened in macOS 15.
If this is true, then apples engineers or managers made a huge mistake in their implementation.
You’re inexperienced in the world not your knowledge.
I also have an M2 Pro with 32GB of memory. When I A/B test with Electron apps running vs without, the lag disappears when all the unpatched Electron apps are closed out.
1. https://avarayr.github.io/shamelectron/
Here's a script I got from somewhere that shows unpatched Electron apps on your system:
Edit: HN nerfed the script. Found a direct link: https://gist.github.com/tkafka/e3eb63a5ec448e9be6701bfd1f1b1...
My MacOS experience has been first party software is getting worse.
Look, if userspace apps can break system functionality, to the level that simple mouse cursor is not responsive, it suggests that there is something fundamental broken in the OS.
Yes, everyone should blame and shame Electron, but here the bug is firmly in the OS.
Electron is most likely using a whole ton more. Apple is sending a message. "Fix your crap or expect more."
- Open a GitHub issue explaining those private APIs shouldn't be used.
- Even better, open a PR fixing their use.
- Make those API calls a no-op if they come from an Electron app.
- Fix those API calls not to grind the OS to a halt for a seemingly simple visual effect.
- Create a public API allowing the same visual effect on a tested and documented API.
Choosing to (apparently violently) downgrade the user experience of all Electron app users, without a possibility to update at the launch day, if a deliberate decision and not an overlooked bug, is a rather shitty and user-hostile move, don't you think?
The _cornerMask override was a hack that shouldn't ever have existed in the first place, and it's not the only use of private APIs in the electron code base.
Apple is very clear about how they want you to make software for their OSes. It's 100% on electron that they choose to do it this way regardless.
I'd go as far as to say Electron itself is a hack that shouldn't exist, but sadly everyone has decided it's the only way they are going to make desktop software now.
(And shit like this is exactly why runtimes like the JVM or the .NET CLR are designed to install separately from any particular software that uses them. Each of their minor [client-facing-ABI compatible] versions can then be independently updated to their latest OS-facing-bugfix version without waiting for the software itself to ship that update.)
Long-term, this is a maintenance nightmare. These hacks can stick around for decades, because there's no backpressure on downstream to actually fix things. It's not about "team velocity", it's about keeping yourself sane.
> - Open a GitHub issue explaining those private APIs shouldn't be used.
> - Even better, open a PR fixing their use.
Apple has a history/culture of secrecy. Whenever they provide public source code, it's a dump thrown over the fence. There is most likely some team inside that actually cares, but they can't "just" open an issue. My guess is that this is their message.
> [...] is a rather shitty and user-hostile move, don't you think?
Yes, I agree, the general direction they've been taking has been increasingly user-hostile for a very long time; let alone the developer story.
But sometimes there's also a perfectly reasonable excuse, from both "technical" and "organizational" POV. That's just my take, a skunkworks effort to get Electron to fix their crap. I would do the same.
The most effective way would be for Apple to actually seek feedback on requirements and then actually implement public APIs for functionality that people need.
Don't really care who is to blame, but they should have identified this, and either warn developers, or warn users. Or provide a tool for identifying guilty apps in your machine, and let users decide how to proceed.
Like I said, *this* is their warning.
If it is accessible from userspace it is by no means private.
Does it mean the API is private in the sense of "unstable" interface? It could very well break the userspace app relying on undocumented behavior, however, crucially here, anything that is exposed to userland WILL at some point be used by some application, be it legitimate or malicious, and it should not break the OS in any way. That's basic hygiene, not even security.
inb4: yes, userspace app could trigger e.g. millions of io operations and millions of number crunching threads and thus cripple the rest of userspace (or at least the rest of userspace at given priority level), yet the system part should still run within performance envelope. Insert "Task Manager (Not Responding)" meme.
So we are talking about public/private access specifiers in source code, which only matter in cooperative setting. But that's IMO highly naive view as compute, especially OS, is objectively an adversarial environment. Some actors, at some point WILL figure out the memory layout and use that in an attack. There have been literally decades of whack-a-mole against bad actors.
I maintain my stance that any fields/members/methods loaded into a userspace program should not be capable of breaking the system.
I'd point fingers towards the electron core devs for this one, and not devs building apps on top of electron (since they likely didn't know that's how electron was doing it).
There are cases where OS companies noticed the use of private APIs and made cleaner public ones (the most obvious was the file system syncing stuff used by Dropbox and others, which used to use private APIs until Apple provided a public one).
And either way, applications shouldn't be able to break the system like this. You can reasonably expect error handling to catch this, even if the error is "a private API was called".
This is on Apple. 90% at least. Maybe 10% on Electron.
If I can walk on land that says private property, it's not private. I'll remember to use that argument when I get ticketed for trespassing.
There are APIs that are explicitly declared verboten for third-parties to use because they aren't intended for outside use. That doesn't make them magically inaccessible, but it does mean that when their unanticipated use breaks things, that's on the people who ignored the warnings.
I agree that this shouldn't be able to have the huge impact that it does and that Apple ought to have made their OS more resilient, but your logic is weak.
> Even in legal matters, it's already the case that laws that aren't enforced are worthless, cf. driving 5-10 mph over the speed limit being normal.
Just because all but one cop of the force ignore people driving over the speed limit doesn't mean the one who pulls you over is isn't able to write you a speeding ticket. Try that with a judge. It might work, but the law is very much still enforceable. This isn't like failing to protect a trademark.
Dude. Dudette. Duderino. Did you think this through before you hit post? I'm talking about enforcement. If you're getting a ticket, it's literally being enforced. And if it isn't, you get squatters! Thanks for the point in support, I guess?
I think this is the most braindead knee-jerk HN comment I've ever gotten as a reply, congratulations.
[Ed.: god, please, this genuinely hurts my brain.]
> but it does mean that when their unanticipated use breaks things, that's on the people who ignored the warnings.
Yeah. When it breaks things for them. Not when it breaks the entire OS' UI.
Let's stay with your analogy. Things change, Electron apps break? That's analog to finally getting around to calling the cops on squatters after dozing on it. Things change, your UI goes belly up due to Electron? That's you deciding to pay the bill for electricity and indoor plumbing for the squatters. No, wait, even better: you decided you finally want to build a new house on your plot, and now have to deal with getting the squatters out first. It'll happen, but you'll have to unnecessarily sink time and money into that. Apple's dealing with evicting Electron off their private APIs. What a nice analogy.
Of course the squatters are technically wrong. But why did you leave your front door open, and neglected and didn't check in for years? The part where you're making it hard for yourself is on you, mate. You're not going to get your lost time back. Why didn't you grab a lock at home depot?
> Just because all but one cop of the force ignore people driving over the speed limit
This is generally policy, not individual cops' discretion.
Wax idealistic all you want, but just imagine the discussion we’d be having if Apple had sigabort-ed all these misbehaving electron apps on day one. “No userland APIs, private or otherwise, should be able to crash your app!!!” Is the argument I would be responding to right now.
> > userspace app could trigger <...> and thus cripple the rest of userspace (or at least the rest of userspace at given priority level), yet the system part should still run within performance envelope
If userspace triggers what is an effectively a DoS attack and you cannot login to root terminal and get things sorted out that's a system not designed for adversarial userspace.
> but just imagine the discussion we’d be having if Apple had sigabort-ed all these misbehaving electron apps on day one
A more general context we are discussing here is resource exhaustion. There are myriads of scenarios where userspace can cause some form of resource exhaustion. My argument is that a 1) well designed 2) general use system should implement resource management in a way (e.g. priority queues) that userspace-inflicted resource exhaustion does not affect performance envelope of the system itself. Otherwise the system is open to unprivileged DoS attacks with only recourse being power cycling.
If your userspace app overcommits memory to some monstrous degree, what should the system do?
1. Enter a swap feedback, crippling the system down to unusability.
2. OOM-kill a process based on some heuristics.
3. freeze userspace, leaving privileged space functional.
The OS got a little slower, that’s it. It was never in some unrecoverable state. One could soft close the offending processes at anytime and regain the lost perf. I’m willing to bet you could hide or minimize the window to mitigate the issue, because the bug is very specific to the layout and render run loop, which auto-pauses on lost visibility by default.
That said, I haven’t even noticed the slowdown on my work machine, but I only use Teams. it’s always been dog shit slow, just par for the course.
I too have a work-provided laptop and a personal one bought the same month, with identical specs (the only difference is the US vs UK keyboard layout). The work-provided one is at least an order of magnitude slower to do anything thanks to enterprise crapware.
* My iPhone as a remote for my Apple TV has randomly stopped deciding it can control the volume - despite the "Now Playing" UI offering an audio control that works.
There auth screens drive me crazy:
* Why cannot I not punch in a password while Face ID is working? If I'm skiing, I know Face ID isn't gong to work, stop making me wait.
* Likewise, on Apple TV the parental control input requires me to explicitly choose to enter a Pin Code. Why? Just show me the Pin Code screen. If I can approve from my device, I will.
* Similarly, if I use my phone as a remote, why do I need to manually click out of the remote to get to the parental control approval screen. I'm literally using my phone. Just auto-approve.Funny, a similar thing has been driving me crazy on my Ubuntu 20.04 laptop with fingerprint login. When unlocking, I can either enter a password or use fingerprint. On boot, I am not allowed to enter a password until I fail with fingerprint. If I use fingerprint to log in on boot, I have to enter my password anyways once logged in to unlock my keychain.
I should probably just figure out a way to disable fingerprint on boot and only use it for the lock screen.
Of course the thin Apple remote has a way of getting lost, but it has a Find Me feature which locates it pretty well.
It seems to have been degrading for a long time, but for me it’s been in this past year where it’s crossed into that threshold android used to live in where using the phone causes a physiological response from how aggravating it can be sometimes
I let my guard down and got too deep into the apple ecosystem- I know better and always avoided getting myself into these situations in the last, but here I am
The phone sucks right now - super buggy and they continue to remove/impose features that should be left as an option to the user By Yes, this has always been the knock on apple, but I typically havent had an issue with their decisions - it’s just so bad now
Lesson (re)learned and I will stay away from ecosystems - luckily the damage here is only for media
The minute I can get blue bubbles reliably on an android, I’ll give the pixel a shot again - if that sucks too then maybe I’ll go back to my teenage years and start rooting devices again
There were many papercuts, but the keyboard being a hundred times worse than Android is what aggravated me every time I had to use the phone, and the straw that broke the camel's back.
I am fully bought into the Apple ecosystem. Not sure yet if I regret it. It is annoying to be so tied down to one company that isn’t going the way I want it to.
There are current workarounds, like isn’t your home Mac as a relay, but nothing super elegant that I know of
this means that i either use ios or i have to be "that guy" always asking everyone to send something in a different format or to please move the conversation to some other app - no one wants to be that guy - apple's got us right where they want us
and to be honest, when texting other people, it makes a huge difference, believe it or not, if your chat bubbles on their screen are blue vs green. it shouldn't matter - people who would care about this aren't people you would want to talk to anyway blah blah - that's all fun and great but it does matter, unfortunately
IMO it’s better than Signal as far as UX goes with enough privacy to be practically for everyday chat. I actively avoid WhatsApp because Facebook. They recently changed their privacy policy to no one’s surprise.
I’ve also been unable to get the remote app on my watch to work at all. It’s hard to imagine people working at Apple don’t also run into these issues all the time.
https://support.apple.com/guide/deployment/wi-fi-ethernet-sp...
No devices support 320Mhz bandwidths, and only supports 160Mhz on 6GHz band on MacBooks and iPads. Some iPhones support 160Mhz on 5GHz as well.
I was at a Wi-Fi vendor presentation a while back and they said that 160 Mhz is pretty improbable unless you're leaving alone and no wireless networks around you. And 320 Mhz even less so.
In real life probably the best you can get is 80 Mhz in a really good wireless environment.
WiFi does currently get anywhere near the bandwidth that these huge channels advertise in realistic environments.
For 6ghz? Yeah, not uncommon.
2.4Ghz is pretty much only used by IoT, you generally don't care about channel width there. When your client device (laptop, phone) downgrades to 2.4Ghz it might as well disconnect because it's unusable.
5Ghz get stopped by a drywall, so unless your walls are just right to bounce off single, you need AP in every room. Ceiling mounting is pretty much required and you're pretty much free to use channels as wide as your device support and local laws allow.
6Ghz get stopped by a piece of paper, so the same as 5Ghz except you won't get 6Ghz unless you have haev direct line of sight to the AP.
https://support.apple.com/en-gb/guide/deployment/dep268652e6...
An infinitely small percentage of people can take advantage of 320Mhz. It's fine.
Reducing Broadcom's influence over the WiFi ecosystem alone would be a large benefit.
But it's a glorified Kindle and YouTube box, so I'm hesitating a little bit.
Which is fine, since it’s exclusively used to watch a kids show for a half an hour a day.
…but it’s also super sad to see a once fantastic piece of kit to degrade so much primarily due to software.
It feels very much like how I imagine someone living in the late 1800's might have felt. The advent of electricity, the advent of cars, but can't predict airplanes, even though they're right around the corner and they'll have likely seen them in their lifetime.
I’ve been debating making a Tumblr-style blog, something like “dumbapple.com,” to catalogue all the dumb crap I notice.
1. I won't focus on a bunch of Siri items, but one example that always bugs me: I cannot ask Siri to give me directions to my next meeting. The latest OS introduces an answer for the first time, though. It tells me to open the calendar app on my Apple watch, and tap on the meeting, and tap the address. (I don't have an Apple watch.)
2. Mail.app on iOS does not have a "share sheet." This makes it impossible to "do" anything with an email message, like send it to a todo app. (The same problem exists with messages in Messages.app)
3. It is impossible to share a contact card from Messages.app (both iOS and MacOS). You have to leave messages, go to contacts and select the contact to share. Contacts should be one of the apps that shows up in the "+" list like photos, camera, cash, and plenty third party apps.
4. You still have to set the default system mail app in MacOS as a setting in the Mail.app, instead of in system settings. Last I checked, I'm pretty sure you couldn't do this, without first setting up an account in the Mail.app. Infuriating.
You can’t directly share the mail message, but you can “share” selected text or you can use the “print” option to generate a PDF of the message and “share” that instead. Not very discoverable but might cover at least some of what you want to do.
Also not sure if it’s new with iOS 26 but for the contacts thing you can at least skip the “leave messages and search for the contact in the contacts app” part. There’s button in the contact info that will take you directly to the contact in the contacts app. It does feel silly that you can’t share direct from the card in messages though.
But, like, man - why can't I just use the arrow keys to select my WiFi network anymore? I was able to for a decade.
And the answer, of course, is the same for so much of macOS' present rough edges. Apple took some iPadOS interface elements, rammed them into the macOS UI, and still have yet to sand the welds. For how much we complain on HN about Electron, we really need to be pissed about Catalyst/Marzipan.
Why does the iCloud sign in field have me type on the right side of an input? Why does that field have an iPadOS cursor? Why can't I use Esc to close its help sheet? Why aren't that sheet's buttons focusable?
Why does the Stocks app have a Done button appear when I focus its search field? Why does its focus ring lag behind the search field's animated size?
Where in the HIG does it sign off on unfocusable text-only bolded buttons, like Maps uses? https://imgur.com/a/e7PB5jm
...Anyway.
I'd love to agree that comically amateurish, but apparently there's something about settings dialogs that make them incredibly difficult to search. It takes Android several seconds to search its settings, and the Microsoft start menu is also comically slow if you try to access control panels through it, although it's just comically slow at search in general. Even Brave here visibly chokes for like 200ms if I search in its preferences dialog... which compared to Android or Windows is instant but still strikes me as a bit to the slow side considering the small space of things being searched. Although it looks like it may be more related to layout than actual searching.
Still. I dunno why but a lot of settings searches are mind-bogglingly slow.
(The only thing I can guess at is that the search is done by essentially fully instantiating the widgets for all screens and doing a full layout pass and extracting the text from them and frankly that's still not really accounting for enough time for these things. Maybe the Android search is blocked until the Storage tab is done crawling over the storage to generate the graphs that are not even going to be rendered? That's about what it would take to match the slowdown I see... but then the Storage tab happily renders almost instantly before that crawl is done and updates later... I dunno.)
Funny I'm defending them, but I think this is not even a papercut in my opinion, while they have far bigger issues.
It should be searching, what, a few hundred strings? What is it doing? Is it making a network call? For what?
Anyway, barely related, but it does bring into question the quality of modern software.
Interested in collaborating on this? Perhaps a simple open-source static blog built with Astro?
Apple has a higher duty to their shareholders than to their customers.
Not hating on Apple, just stating the hard economic truth.
PS The Earth isn’t flat. We did go to the Moon. Vaccines don’t cause autism.
From the 2005 iPods settlement [0], to the 113 Mio USD Batterygate [1], to Flexgate [2] where Apple only escaped settlement due to plausible deniability.
To quote from Batterygate:
> Apple has agreed to pay millions of dollars to 34 states over its controversial previous practice of deliberately slowing down older iPhones to extend their battery life.
> [...]
> Many believed it was an effort to encourage users to buy new iPhones.
I agree on all your "PS" points, where we seem to differ is that reading is a virtue and not knowing something because you haven't heard of it doesn't constitute a conspiracy theory.
0: https://www.cbsnews.com/news/ipod-class-action-suit-settled/
1: https://edition.cnn.com/2020/11/19/tech/apple-battery-settle...
2: https://www.macrumors.com/2021/07/20/flexgate-class-action-l...
Flexgate is a manufacturing error, that they handled in a consumer hostile way
Batterygate, was an arguably misguided way to support outdated models - prioritising one goal (battery life) over another (speed)
The iPod thing I’ll admit I know nothing about.
It sounds like, for you, planned obsolescence is defined as any instance where a product isn’t manufactured perfectly or degardes over time, regardless of whether it was planned. For me, planned obsolescence should contain at least a hint of planning.
Maybe, but for lots of scenarios even M5 could still benefit from being an order of magnitude faster.
AI, dev, some content scenarios, etc…
Apps used to use less ram but over the years apps have become big and more complicated. This is probably why iPhones feel sluggish because new iPhones have more memory and apps snap back faster as newer iPhones which also have faster storage and memory bandwidth to reduce latency of reading more data from the flash.
Batteries are also a problem as maintaining voltage is difficult for a 2-3 year old battery. An official battery swap at apple service for a 3 year old iPhone will make it run much better.
I used to believe (and sometimes I still do) that apple intentionally makes everything heavier to make old phones and devices feel slower but I don't think thats the case.
I think that more things are happening on newer phones and devices and that same task feels slower on older device. This happens are lot faster on iPhones and phones in general (a year or two) as opposed to Macs/computers which can show signs of aging in 4-5 years.
My 2018 intel computer feels very slow in 2025 running Gnome. No one slowed it down. It's just that the 2025 world of software is a lot heavier and 2026 will be even more and so on.
Not really sure what else they could have done there.
My old iPhone 7, before I eventually replaced it, would sometimes just die due to this as the battery aged (I kept the slowdown setting turned off). AFAIK it is _not_ a thing in any version after the 7 (or maybe 8?); certainly my 11 had a significantly degraded battery by the end (I kept it for four years), and didn't suffer this issue.
EDIT: Actually, I think this article is a _little_ inaccurate, or at least confusing:
> thus preventing the handsets from rapidly running out of juice and powering off.
IIRC the issue was, more precisely, that the SoCs had insufficient voltage smoothing to reliably tolerate full power draw at lowered voltages, and would shut off randomly. I assume the fix was, pretty much, more capacitors.
n=1.
I also have a 2018 iPad Pro and put iPadOS 26 on it and I haven't had any issues on it either except sometimes my keyboard is slow to connect. I'm not sure if it's the software or hardware though.
There's plenty of room for criticism without a blanket conspiracy that doesn't match what most can observe.
Sad if true. I feel my M1 max sluggish too lately. After bragging that this was the longest lived work machine I had and thinking I'm good to wait for M6. This is not good for business, but IMO you need more than raw power to justify upgrades even for professional use - form factor, screen quality, battery, etc.
I think they bet a lot of hardware money on AI capabilities, but failed to deliver the software, so there was no real reason to upgrade because of AI features in the chip (which is literally what they boast on the first line of the announcement - yet nobody cares about making more cute faces)
It's not 100% their fault. Everyone got onto the LLM bandwagon like it's "the thing" so even if they didn't believe it they sill needed something. Except an OS is not a chat interface, and LLMs do suck at stricter things.
a rant on my part, but a computer from 10 years ago would be fine for what most people do on their computer, only for software bloat..
Counterpoint: my M1 Pro was a turtle for a few weeks and then stopped doing nonsense in the background and is back to its zippy self. (Still buggy. But that would be true on new hardware, too.)
I would love to se a ThinkPad with an M5 running Linux.
I kid, I kid.
Is that good? Their cellular modems have been terrible. I'll reserve judgement until trying one out.
>The M1 itself is so powerful
I think this is a bit of a fallacy. Apple Silicon is great for the power consumption to power ratio, but something like a Ryzen 9 7945HX can do 3x more work than an M1 Max. And a non-laptop chip, like an Intel Core Ultra 7 265k can do 3.5x.
https://browser.geekbench.com/processors/amd-ryzen-9-7945hx
https://browser.geekbench.com/processors/intel-core-ultra-7-...
https://browser.geekbench.com/macs/macbook-pro-16-inch-2021-...
https://browser.geekbench.com/macs/macbook-pro-16-inch-2024-...
Performance claims:
https://www.ookla.com/articles/iphone-c1-modem-performance-q...
Energy claims:
https://appleinsider.com/articles/25/02/27/apples-c1-modem-b...
I also installed the iOS 26 update recently. The competitive advantage of software polish that Apple had seems totally gone.
Add to that bugs in iCloud, AirDrop... I don't think I will be buying any more Apple devices for myself.
Disclaimer, i actually like a bit of "bling", but both Tahoe and IOS so filled with glitches and errors, while the UX is bizarrely inconsistent it really is catastrophically bad.
Naturally Apple as the survivor from all that were not IBM-PC, appears to be the one with vertical integration approach.
I keep hearing this since the Intel 486DX times, and
> Nobody will ever need more than 640K of RAM!
Amusingly enough, adding more ports could do it.
Devices get slower for no perceivable reason, when in reality software at all levels makes higher assumptions about how much power you have, and squanders it more readily.
I am undecided in my thoughts about how malicious this is. Do people think that it is something like wanting to cram more features into the operating systems, and they are careless how it affects the earliest supported models? Or do most people think it is planned obsolescence?
Apple generally offer updates longer than Android, so is it more pronounced on iPhones than Android phones? I remember seeing similar slow-downs on Android phones in the past.
Apple generally offer updates for iOS for less time than Windows. I don't really have a feel for the difference between the two in terms of how much new versions slow down older hardware.
Obviously separating feature updates and security updates would be a way to address, and it's not possible that no one at Apple has considered that idea. They are a business and selling new products is unfortunately a disincentive pushing them away from doing that.
They did make a mistake, though: they should have been up-front about it. They should have advertised it rather than hiding it away.
Not going to happen, but I can dream.
I think many IT departments will be thankful for that as Wifi behaviour can be challenging and hopefully will lower ticket counts.
1] Which I still firmly believe WAS indeed a power-supply design failure that would have forced a massive hardware recall had they not done something (slowing down the os). I believe it encompassed everything from inaccurate CPU power estimates to something actually incorrect with the PCB design, causing brown outs - and not merely a battery-aging red herring as is the reported scandalous reason they were "caught". In fact, I think Apple is GLAD that all it amounted to was some philosophical hullabaloo about protecting your poor aging battery.
To clarify, I suspect the "aging battery" merely exposed the real issue - the incorrect PS design - which Apple successfully covered up.
Quit the Dropbox app, it’s electron, and it’s brand spanking new
WatchOS 26 has rendered my Apple Watch almost useless. It's gone from lasting a whole day including 2 cycling 'workouts' for my commute and the occasional lunch time run (or gym session before work) to now being at 40% battery by the time I make my mid-morning coffee and dead before I get home.
I don't use most of the 'smart' features anyway - I'm mostly using the fitness features - so I'll probably switch to a Garmin at some point.
If that's your use case, I can absolutely recommend getting one. I have a Forerunner 745 and it works great for workouts alongside some smart functions like NFC payments, quick-replies to texts, etc. The battery lasts for days as well, which you can't really beat.
The Garmin Instinct 2X's (and 3) battery lasts for 40 days in smartwatch mode, not counting the solar charging.
The Instinct is an "outdoor watch" with a monochrome display, but it has most features the Forerunners have.
- Suunto (20 to 30 days in smartwatch mode for the Verticals, optional solar charging, flashlight on the Vertical 2)
- Coros (2 to 3 weeks depending on the model), no flashlight
- Withings (30 days, looks like a regular watch)
Coros is good for how long they support their watches, and the fact that they don't restrict features in lesser models. Suunto is great for route planning. Polar is renowned for its training metrics (sleep, recovery etc.) but only fetches a week in smartwatch mode.
Edit: Same experience with iPhone X
Edit2: I still remember the feeling when I got them initially - that Apple is on customer's side, but now I feel totally helpless and i'm being forced to upgrade
I've got a reference macbook air from 2015, which is almost clean, only zoom, teams and chrome for meets are installed and used for calls. And boy, how do I regret making macOS updates.. I can believe teams and zoom are shitbags of modern software slop, and thus started to fail running simple video calls. But even native macOS apps that are barely updated for years like notes and calendar are freezing now. So I can conclude that these anti-backward compatibility updates are highly intentional, because hardware is absolutely fine for decade, i even used this ultra-tiny air for travel work once back in 2022, it was still capable to do all office things and thin client. But last year it just turned into pumpkin.
My question is - maybe installing linux can help bring it back to life.
That really is a reason for me to skip this upgrade and wait for the next release.
They are so scared about cannibalizing mac/ipad sales - they really really want people to own both.
This gets rid of the slow animations, inconsistent window cornering, and other annoyances.
Then (so menus aren't transparent and unreadable): System Settings > Accessibility > Display > Reduce Transparency
If you do those two things your machine should look and feel normal again. I've been running an M1 Max since 2021 and Tahoe was simply a disaster. Removing the glass layer made everything feel good again.
If for some reason you ever want the bad performance and glass back, you change the YES to NO in the Terminal command. Maybe someday it won't suck.
I really don't like what it does to certain transparent drop downs for certain apps as well as the control center.
But It does seem nice to do it on a per app basis (ie "defaults write com.apple.finder com.apple.SwiftUI.DisableSolarium -bool YES")
https://tidbits.com/2025/10/09/how-to-turn-liquid-glass-into...
I personally have no idea but I seem to recall the golden age of open source/unix embrace was under Serlet
All in all, apple is doing some incredible things with hardware.
Software teams at apple really need to get their act together. The M1 itself is so powerful that nobody really needs to upgrade that for most things most people do on their computers. Tahoe however makes my M1 Air feel sluggish doing the exact same tasks ive been last couple of years. I really hope this is not intentional from Apple to make me upgrade. That would be a big let down.