Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

221–227 of 227 posts

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

#221

Post by tyteen4a03 »

kccqzy wrote: 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…

Reminds me of this line of code where Apple included a symbol just to please an app (which happens to be WeChat, the largest IM app in China): https://github.com/apple-oss-distributions/libmalloc/blob/13...

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

#222

Post by inDigiNeous »

taroth wrote: post #167

One-liner for electron developers to fix the issue: `browserwindow.setHasShadow(false)`

Thank you for this!

Could possibly just hotpatch my existing app, add this to the packed in javascript .asar resource file and not having to make a new build with updated Electron version.

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

#223

Post by inDigiNeous »

rayiner wrote: post #174

Individuals used to make sophisticated native apps as shareware for $10 back in the 1990s and today big teams rely on crap like Electron. The enshittification of everything.

Well, back in the day you had 4 megs of ram, MS-DOS and other OSes that are simple as they come, and full access to the hardware.

These days if you want to support macOS, Windows, Linux: I say good luck to you, Electron can save you there.

Electron is not crap, but many javascript developers are crap. You can make fast and memory efficient apps in Electron, if you know how to code.

(Note: Slack or Discord developers don't have that skill)

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

#224

Post by pacifika »

modeless wrote: post #69
reaperducer wrote: post #60

Earlier quoted context omitted.

Awesome if you're a one-man-band. Not awesome if you're in a large company where you have to communicate with others and don't get to choose the medium.

I find Slack and Discord to work fine in browser tabs and never felt the need to install their desktop apps. VSCode/Cursor is the only Electron app I felt actually provided value.

For Slack the huddles work better in the app

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

#226

Post by leakycap »

rpgbr wrote: post #146
torben-friis wrote: post #13

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'm doing my job: https://manualdousuario.net/en/liquid-glass-2/

Great writeup & points. I can't imagine sticking with Mac all this time if I had started on the rough 10.10 release.

> It’s a rare misstep from Apple — and an unprecedented one in scale.

There's a lack of taste & lack of respect for the user, too. Things that usually don't get fixed in point releases and take a long time to course-correct.

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

#227

Post by leakycap »

torben-friis wrote: post #171
rpgbr wrote: post #146

Earlier quoted context omitted.

I'm doing my job: https://manualdousuario.net/en/liquid-glass-2/

I won’t lie, with today’s apple the implied possibility that the resource hungry style is intentional is believable.

I think the goal was to do something competitors could not easily pull off. They failed, but I think that was the goal.

With Android's diverse/fractured ecosystem, a similar "system wide" look with reflectivity would be hard to deliver across the board on Android with so many models having very bare specs.

Post reply on HN