Earlier quoted context omitted.
The most inefficient solution (in both space and time complexity) Those are not the only qualities / metrics to optimize for. Developer eXperience, cross platform, open standards, easy compatibility with websites, easiness to keep updated etc. can be far more important
Developer experience is never more important than the quality of the end product. The goal is to make good software, not to have the easiest time possible making mediocre to bad software.
Electron-based apps cause system-wide lag on macOS 26 Tahoe
161–170 of 227 posts
Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#162Earlier quoted context omitted.
> 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. Thos…
I don’t understand what goes through the developer’s mind. A method is marked as private. It’s documented as not to be used by developers. Further documentation says that using it may break your application in strange ways now or in the future. Despite all this, the developer concludes: “yea, I think it’s a good idea to use this API!” Then, later when something breaks, it’s Shocked Pikachu all around.
This isn't really true. When something breaks it's generally "darn, we knew it would happen eventually".
Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#163It's not limited to Electron applications: https://github.com/neovide/neovide/issues/3225 Other Tahoe issues with non-Electron apps: https://github.com/zed-industries/zed/issues/33182 https://github.com/wezterm/wezterm/issues/7255
GPU load bug and Autofill bug are two separate, completely unrelated issues.
Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#164Well, 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.
1. This is about a specific bug, not about Electron in general. 2. What better cross platform GUI alternative do you suggest?
Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#165Earlier quoted context omitted.
VS Code package in my applications folder is 600+ MB. The Electron Framework.framework it contains is 400+ MB alone. I don't understand where you come up with your 90 MB figure?
The VSCodeUserSetup file from https://code.visualstudio.com/download is in the 90MB range. Perhaps this file is just the installer and the actual system files are much larger? Or maybe your 400MB figure comes from a bloated install? Just speculating here.
Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#166Earlier quoted context omitted.
> 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. Thos…
I don’t understand what goes through the developer’s mind. A method is marked as private. It’s documented as not to be used by developers. Further documentation says that using it may break your application in strange ways now or in the future. Despite all this, the developer concludes: “yea, I think it’s a good idea to use this API!” Then, later when something breaks, it’s Shocked Pikachu all around.
Of course, if you use a private API, you're on your own if your app breaks because of it. I myself have done my fair share of using private APIs on Android. Ideally, you should test your app on beta versions of every upcoming major OS release to make sure it doesn't break. Even more ideally, there's a public equivalent starting with some OS version and you only use the private one until that version, then nothing will ever break.
Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#167`browserwindow.setHasShadow(false)`
Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#168It's not limited to Electron applications: https://github.com/neovide/neovide/issues/3225 Other Tahoe issues with non-Electron apps: https://github.com/zed-industries/zed/issues/33182 https://github.com/wezterm/wezterm/issues/7255
This might be the fix: https://github.com/ghostty-org/ghostty/pull/8625/commits/431...
browserwindow.setHasShadow(false)
Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#169Re: Electron-based apps cause system-wide lag on macOS 26 Tahoe
#170Earlier quoted context omitted.
I don’t understand what goes through the developer’s mind. A method is marked as private. It’s documented as not to be used by developers. Further documentation says that using it may break your application in strange ways now or in the future. Despite all this, the developer concludes: “yea, I think it’s a good idea to use this API!” Then, later when something breaks, it’s Shocked Pikachu all around.
I get it but a lot of the war stories from Raymond Chen's blog https://devblogs.microsoft.com/oldnewthing/ were about helping major corporations unscrew something that had relied on a private Windows API because there hadn't been a good way to do it. I would guess most cases of people choosing to rely on a private method are laziness or lack of knowledge about "the right way" (or call it bad documentation), but not 1…