https://github.com/electron/electron/issues/48311#issuecomme... If this comment is to be believed, it's not Apple's fault. It's the apps mucking around with the internals of AppKit. This example just happens to illustrate two of my least favorite software engineering practices: (1) despite one piece of code making a method private, another piece of code still overrides it/modifies it/calls it, an affront to the idea…
A good argument for allowing and working with minor platform differences instead of trying to micromanage every little aspect to force inter-platform consistency and/or perfect compliance with the mockup.
I know it's a defacto complaint to leverage against Electron apps, but memory usage notwithstanding, I've never run into much lag issue on any major Electron app.
It depends. Numerous times when internet is spotty Slack and Discord both on different occasions have brought my systems to a halt until they can complete whatever task is stuck waiting (or I force close them). It's really fucking obnoxious that somehow a goddamn web app in a wrapper is managing to cause system wide hangs.
True, i'm gonna start limiting electron apps CPU and IO percentage to not halt everything
I’m surprised to see so little pushback in press to iOS/macOS 26. I’ve been part of the public beta and it’s been so weird going from “this sucks but it’s a first beta” through “it really isn’t improving much as time goes by” to “we’re a week from launch, there’s no way they release this after the Apple Intelligence fiasco”. And yet here we are. Performance issues, ui inconsistencies and garish design everywhere.
> Performance issues, ui inconsistencies and garish design everywhere.
Hasn't that been Apple's norm for a few years now?
Not trying to land a cheap dunk here; I've honestly been running into rough edges and bad design with every major release for a long time.
https://github.com/electron/electron/issues/48311#issuecomme... If this comment is to be believed, it's not Apple's fault. It's the apps mucking around with the internals of AppKit. This example just happens to illustrate two of my least favorite software engineering practices: (1) despite one piece of code making a method private, another piece of code still overrides it/modifies it/calls it, an affront to the idea…
"Not Apple's fault" is up for debate; even if Electron shouldn't be doing this, Apple arguably shouldn't be pushing out updates that cause issues with wide-swaths of software that users use regardless.
So you're blaming because they've changed a private API which electron not only used, but also seemed to have patched?
https://github.com/electron/electron/issues/48311#issuecomme... If this comment is to be believed, it's not Apple's fault. It's the apps mucking around with the internals of AppKit. This example just happens to illustrate two of my least favorite software engineering practices: (1) despite one piece of code making a method private, another piece of code still overrides it/modifies it/calls it, an affront to the idea…
"Not Apple's fault" is up for debate; even if Electron shouldn't be doing this, Apple arguably shouldn't be pushing out updates that cause issues with wide-swaths of software that users use regardless.
That’s the principle that prevented Windows from making any meaningful progress for the past three decades.
Discord and VSCode work smoothly for me on an M4 MBP -- not sure if it's a compatibility difference or just performance hiding the problem, though. But Spotlight file search is completely broken, rebuilding the index doesn't help, and web results are the only thing it returns. After 20 years of intense research, Apple finally caught up to Microsoft in race to make search broken and useless.
> But Spotlight file search is completely broken, rebuilding the index doesn't help, and web results are the only thing it returns. I had the same issue; killing Spotlight processes fixed it. (A reboot would probably do the job too.)
https://github.com/electron/electron/issues/48311#issuecomme... If this comment is to be believed, it's not Apple's fault. It's the apps mucking around with the internals of AppKit. This example just happens to illustrate two of my least favorite software engineering practices: (1) despite one piece of code making a method private, another piece of code still overrides it/modifies it/calls it, an affront to the idea…
"Not Apple's fault" is up for debate; even if Electron shouldn't be doing this, Apple arguably shouldn't be pushing out updates that cause issues with wide-swaths of software that users use regardless.
Apple’s attitude here is that it’s an inherent risk of using private APIs, because it’s not something they want devs doing. They don’t facilitate it like MS tends to. Don’t touch the stove if you don’t want to get burnt.
Discord and VSCode work smoothly for me on an M4 MBP -- not sure if it's a compatibility difference or just performance hiding the problem, though. But Spotlight file search is completely broken, rebuilding the index doesn't help, and web results are the only thing it returns. After 20 years of intense research, Apple finally caught up to Microsoft in race to make search broken and useless.
M4 works great for me. M1 Max with 64gb of memory consistently has issues.
I’m surprised to see so little pushback in press to iOS/macOS 26. I’ve been part of the public beta and it’s been so weird going from “this sucks but it’s a first beta” through “it really isn’t improving much as time goes by” to “we’re a week from launch, there’s no way they release this after the Apple Intelligence fiasco”. And yet here we are. Performance issues, ui inconsistencies and garish design everywhere.
> Performance issues, ui inconsistencies and garish design everywhere. Hasn't that been Apple's norm for a few years now? Not trying to land a cheap dunk here; I've honestly been running into rough edges and bad design with every major release for a long time.
I’m surprised to see so little pushback in press to iOS/macOS 26. I’ve been part of the public beta and it’s been so weird going from “this sucks but it’s a first beta” through “it really isn’t improving much as time goes by” to “we’re a week from launch, there’s no way they release this after the Apple Intelligence fiasco”. And yet here we are. Performance issues, ui inconsistencies and garish design everywhere.
Yeah, screen time for kids is absolutely broken in iOS 26.
I'm glad I'm not the only one experiencing this. They absolutely destroyed Guided Access in iOS 26 to the point of borderline non-functionality. I've had the system idle-sleep while in Guided Access and wake to a lock screen that I was unable to interact with in any way, including turning off guided access. Softlocked my device for about 5 minutes until panicked swiping and button mashing managed to snap it out of it. There appears to be a race condition with the lock screen and home screen, if the device idle sleeps in guided access mode then about 50% of the time it wakes to the home screen instead of the app. Sometimes waking it on iOS shows the lock screen for a brief second before the app starts. Also, exiting guided access sometimes doesn't recolor the apps on the home screen so it still appears as if all apps are disabled. Not to mention that they reclassified the pen settings dialog as a "software keyboard" meaning that in order for my kids to draw with the Apple Pencil I also have to allow them to enter text now. None of these were issues on iOS 18.