> not being too opinionated about your use of memory
That's a bit hard to tell, isn't it? When I checked out the docs after last week's Zig thread, the entire section on memory allocation was a big fat TODO.
This is meaningless without context, as editors typically run indexing processes in the background. I used to use $beloved_native_editor, which in some cases ran at 100% single-thread for extended amounts of time (due to indexing).
> It takes an age to load. It uses heaps of RAM with no projects open [...] I have never seen a single use of it where it doesn't use an extraordinary amount of RAM
I've taken some real-world measurements, with the disclaimer there is no universal interpretation of measuring memory:
>>note taking or chat apps need several hundreds of megabytes of RAM to run.
I have a fairly big app and while I'm not sure how to measure that I ran "about:memory" in Firefox and added up everything I saw for the app and it came out to be about 30mb.
My Mac's Finder says the directory with all the code is 9.9 MB.
That app is plenty fast, even on my old late `09 Mac Mini Mac running 10.11.6 with just 4gb ram.
Windows 10 has had memory compression [1] for quite a while now. On the PC I am on at the moment with 100+ Chrome tabs open, I have 1.3GB compressed out of a total of 16GB.
> It is in the best interest of everyone to make applications use less memory, since all the applications (and the OS) have to share what the system has.
There is always a trade-off between speed and memory usage. For my use cases, I prefer this particular trade-off for a browser. I realize you might not have the same preference.
> About 1GB of memory is required to run the phone with its default scopes and settings, leaving us about 2GB of space for applications and other features.
I did not see this coming. I was under the impression that moving away from a JVM would have lowered the memory requirements.
A comparison of the two versions of Meizu Pro 5, Android and Ubuntu, would have been useful too. I am curious if the move away from the Android architecture has changed the responsiveness of apps, or affected battery life.
> IDEs such as IntelliJ can easily consume 8GB of memory
Sound more like a Jetbrain ( IntelliJ company ) problem. Used to develop on PHPstorm ( another Jetbrain ) product ( same software in the background ) and the slow startup's, 2GB+ memory eating for relative small projects, crashes way too much, expensive as hell for what it does ( especially with the license change years ago ) ...
Eventually switched to Visual Studio Code and while people whine how Electron is memory inefficient, its like 1/6 the memory usage of PHPstorm, with only a few features missing.
Even on a 32GB PC system, i barely use 16GB ( and WSL2 is eating up a lot with a lot of docker images. And its not really docker, just Linux cache eating up memory ). Not a issue on a Mac that does not need a VM like layer.
Its about priorities sometimes. If people keep upgrading their memory, developers/companies simply push the responsibility to the clients and do not bother with spending time on optimizing.
If people start leaving software product on the way side for being just horrible inefficient messes, then maybe a bit of focus will come back to actually optimizing products! You will see Jetbrain change tune, when VSC etc keep eating its market share.
> Vue 3 has demonstrated significant performance improvements over Vue 2 in terms of bundle size (up to 41% lighter with tree-shaking), initial render (up to 55% faster), updates (up to 133% faster), and memory usage (up to 120% less).
Regarding Zend Engine, does anyone have a link for just how much 'less'?
reply