Earlier quoted context omitted.
That's good for you and I'm glad you're happy but for some of us, considering the work with are doing, sometimes even 32GB is not really enough. Different people, different needs.
Too many electron apps? :P
Linux Desktop on Apple Silicon/M1 in Practice
101–110 of 149 posts
Re: Linux Desktop on Apple Silicon/M1 in Practice
#102Earlier quoted context omitted.
Indeed, it is. 16GB is too constrained even for native Linux desktop environment.
Linux desktop environment runs fine with 4GB.
Re: Linux Desktop on Apple Silicon/M1 in Practice
#103Earlier quoted context omitted.
Linux desktop environment runs fine with 4GB.
I think the people who claim that 16 GB isn't enough are insane, but it should be said: at 4 GB it does become a bit problematic to both keep browsers with a bunch of tabs open and do other things smoothly. If we keep modern website hogs out of the picture, I completely agree with you. I tally about 500-1000 MB doing my job – if I can close the browsers that I do admittedly need to read documentation.
Re: Linux Desktop on Apple Silicon/M1 in Practice
#104I imagine memory will be quite constrained here for a lot of M1 systems.
The M1x benchmarks that recently leaked show that it supports 32 Gigs of RAM, has twice the number of big CPU cores, and twice the GPU cores. https://www.tomsguide.com/news/macbook-pro-m1x-benchmarks-ju... It should be adequate for a non-entry level laptop. One of the fairly accurate Apple leakers, Jon Prosser, has said that one of his proven sources has informed him that the leak is legit.
Re: Linux Desktop on Apple Silicon/M1 in Practice
#105Earlier quoted context omitted.
I wonder when the pendulum will swing back and people will stop this insanity. I can already picture the buzzwords people will invent to describe "apps running on the OS itself ".
That would require people to clean up. Sometimes I squint at the installation requirements and then head over to hub.docker.com. I think it will get worse (i.e. more layers on top) before it gets better.
Re: Linux Desktop on Apple Silicon/M1 in Practice
#106Earlier quoted context omitted.
Good luck compiling large sources on 4gb
2GB of RAM user here, done that with clang as it uses far less memory than GCC.
Re: Linux Desktop on Apple Silicon/M1 in Practice
#107What's the story with OpenGL on macOS? I know it is abandonware in favor of Metal but are there reasons Apple will at least keep it in the OS / drivers for foreseeable future? Do any of the ANGLE type things help when they finally take it away?
It still works and at least somebody still seems to work on it going by the somewhat random GL-related fixes and regressions in macOS Betas since GL was declared deprecated. AFAIK ANGLE (and MoltenGL) only provide GLES2.x and GLES3.x over Metal, so out of the box those wouldn't be very useful for providing desktop-GL compatibility. Apparently Zink on top of MoltenVk on top of Metal works, but that looks like a Jenga…
My recommendation is to use Wayland, and to play serious games on macOS (although such games are not available on Linux AArch64 anyway...)
Re: Linux Desktop on Apple Silicon/M1 in Practice
#108Earlier quoted context omitted.
Indeed, it is. 16GB is too constrained even for native Linux desktop environment.
Running Fedora/GNOME on an i5/8gb laptop, never ever felt memory constrained.
Re: Linux Desktop on Apple Silicon/M1 in Practice
#109Would any of this work be useful to run Linux on an iPad?
Re: Linux Desktop on Apple Silicon/M1 in Practice
#110Earlier quoted context omitted.
I think the people who claim that 16 GB isn't enough are insane, but it should be said: at 4 GB it does become a bit problematic to both keep browsers with a bunch of tabs open and do other things smoothly. If we keep modern website hogs out of the picture, I completely agree with you. I tally about 500-1000 MB doing my job – if I can close the browsers that I do admittedly need to read documentation.
> I think the people who claim that 16 GB isn't enough are insane The problem is containers. Some development workflows appear to require running a container for every piece of software needed, and that adds up (and feels incredibly wasteful). None of my development workflow requires containers locally, so I get by just fine with 16gb.
Even this makes little sense unless your containers are really poorly sized. I used to run a mini Kubernetes cluster on my desktop with 6 nodes. Some of them running big Java projects, Postgres, Elastisearch, and Ruby. And I still had enough memory to run Rubymine or IntelliJ along with Slack and whatever other local stuff I needed.