←back to thread

OpenGL 3.1 on Asahi Linux

(asahilinux.org)
512 points simjue | 1 comments | | HN request time: 0.269s | source
Show context
baq ◴[] No.36213345[source]
Related: does anyone do development on a Mac in a Linux VM? If my dockers are already running in a VM, why not go to the next logical step?
replies(8): >>36213449 #>>36213574 #>>36213616 #>>36213903 #>>36217254 #>>36217884 #>>36219930 #>>36220610 #
1. jlokier ◴[] No.36220610[source]
I have done so for years on my 2013 x86 MBP, using VMware Fusion.

It's really nice being able to four-finger swipe between Macos and Linux full-screen desktops when I want that.

But usually I SSH into the Linux VM so that I can use iTerm2 as my terminal, and use Mac native GUI Emacs (railwaycat & Mitsuharu Yamamoto's version) to have its graphical features working alongside my iTerm2 and Firefox.

Linux in a VM runs some things much faster than the host MacOS on the same laptop! In particular filesystem intensive builds. I found some Docker-based test system I had to use for work ran an order of magniitude faster in the Linux VM than with Docker on the Mac host.

I did test running Linux natively on this MBP (no MacOS host) but found to my surprise the battery drained faster than using it in a VM, and the VM is almost as fast. So I stick with the VM and I get to use both OSes side by side.

I don't use the VMware file sharing as it is extremely buggy and regularly corrupts files when operating on them with Git or some other activities due to buggy cache settings which cannot be set to non-buggy values.

Instead I use some crazy combination of Samba and NFS which works reasonably to get the right permissions and ownership as seen by each side of the other's files. The upshot is two-way file sharing works, but this was actually difficult to make reliable.

(I found the Mac SMB2 client is prone to occasionally deleting files that aren't even being accessed by it at all, but are in a directory where other files are being updated. A shocking bad SMB2 protocol bug in the Mac client where it sends the wrong filename for renames occasionally, using a name from a recent directory listing. It took me a year to diagnose that and I thought it must be a bug in my code in a critical Linux database application I was writing, which I didn't dare deploy upstream for all that time, because important random files like invoices and data files would occasionally disappear and be noticed days later causing me to doubt myself. That is until I did a very deep dive with every debugging tool you can imagine, to find the true cause was MacOS when I edited unrelated files, and my application had been fine all that time to deploy to prod. Solution was force MacOS to use CIFS instead of SMB2.)

I hope to replicate something like that when I get an ARM Mac at some point, though I hope the MacOS SMB bugs are fixed. Currently holding out for an M3.