Re:Apple has a memory problem and we're all paying for it
by flohofwoe on Friday November 10, 2023 @02:40AM
(#38216207)
Native apps aren't automatically less bloated, take Xcode vs VSCode for instance. Native apps might just have more optimization potential, but that doesn't mean that the potential is realized. The most efficient applications are 10 or 20 years old, running on modern hardware ;)
[ Parent
| on HN ]
Re:Apple has a memory problem and we're all paying for it
by coldtea on Friday November 10, 2023 @03:09AM
(#38216359)
>Native apps aren't automatically less bloated, take Xcode vs VSCode for instance
What about them? XCode is quite efficient with memory, and it by definition doesn't pass everything through a interpret+JIT for a higher level language.
Re:Apple has a memory problem and we're all paying for it
by flohofwoe on Friday November 10, 2023 @03:15AM
(#38216401)
IME (and I work with both every day), Xcode is slower for almost every UI interaction than VSCode on the same machine. It already starts with Xcode's extremely slow startup, just now it took 15(!) seconds for Xcode to cold-start. And that's on a 32 GBytes M1 Pro.
Re:Apple has a memory problem and we're all paying for it
by fingerlocks on Friday November 10, 2023 @07:05AM
(#38217876)
It really depends on the size of the workspace your loading.
Try opening some heinously large project with 100+ dylibs (react-native) compared against a lean, statically linked single module workspace. You can have them open side by side and it’s like experiencing hell and heaven simultaneously.