Live data from Hacker News

Electron-based apps cause system-wide lag on macOS 26 Tahoe

github.com

31–40 of 227 posts

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#31

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 think you mean “since release”.

Hasn’t it always had horrible problems? I’ve never heard a good thing about it in use.

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#32
post #2

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…

Nah, it's Apple's fault. Not regression testing against major apps is pure incompetence.

Also, this in the comment:

> [a user] Please try any way of getting in touch with Apple engineers you can. As a project, we don't have a better connection to Apple than you do.

>

> One approach might be the engineer who replied to the Bluesky post that someone linked to above about the input issue.

Pure incompetence. Major projects have no way to do anything but ping randoms on socials.

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#34
post #2

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…

> 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 of encapsulation

That's inherent on the way current computers manage the memory. And I don't know if the gains are enough to pay for the loses of guaranteeing encapsulation.

One could reach for static analysis, but that would imply some restrictions on the machine's assembly. Those are probably worth it.

> a piece of code has different behavior depending on the identity of a function

I have written my quota of "find the latest caller on the stack with property X, verify if it has access", on different languages. Some times a function can't in any way be just a function.

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#35

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.

[deleted]

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#36
post #25
post #19

Earlier quoted context omitted.

"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.

What? Windows made tons of progress while maintaining this principle and became the most popular operating system in the world. Are you trying to tell me that you believe the evolution of Windows from 1.0 all the way to 7 - the entire time trying to operate according to this principle - doesn't constitute meaningful progress?

The recent stagnation of the OS has nothing to do with attempting to maintain backwards compatibility.

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#37
Well, that's...Electron for you.

The most inefficient solution (in both space and time complexity) being suggested to build desktop apps is now shown to be causing widespread sluggishness.

So much for interviewing developers for algorithms and data structures. Also Rust won't save you or make Electron faster either.

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#38

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.

[deleted]

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#39
post #19
post #2

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.

We've had developer betas of macOS Tahoe since June.

Standard practice for any mobile or desktop software is to start testing on the betas as soon as they're available. Unless this was a last-minute change before the final release, it's on the software developers to use the betas to prepare their software for upcoming releases.

Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe

#40

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.

I was going to wait for a few bugfixes until I upgraded, but I was forced to update to iOS 26 because the AirPods Pro 3 that I bought required it for some inexplicable reason (which I didn't know until I tried to pair them). The AirPods are just fantastic in every way and a huge leap forward, I don't regret buying them for a second. But sheesh, none of the OS updates were ready for release. I found 3 obvious bugs (non-functional UI elements, invisible labels due to incorrect handling of dark mode, soft locks caused by guided access) not to mention a distinct pause when unlocking the device, GPU issues with Safari. It seems like the pendulum has swung from Apple making mediocre overpriced hardware and reliable software, to making best-in-class hardware and garbage software. I'm hoping that with the end of Intel support we get a "Snow Leopard" style polish and bugfix of the entire stack, but with their recent track record it seems unlikely. It's just inexcusable for a company with Apple's focus on consumer products and market cap. At least Microsoft has the excuse that they have a sprawling empire to oversee.
Post reply on HN