On: macOS Sonoma Forced Installs

[FredPret]

> Meanwhile, my Windows machine updates itself whenever, often even in the middle of overnight computing tasks.

This pushed me to Mac. Being more Unix-like, it's vastly better in terms of the control I have over the system. But I'm still not a 100% owner of my platform, so I now use an actual Linux server to run compute tasks.

There's a nice synergy between using Mac and Linux - many of the same scripts, commands, and concepts work identically.

[magnio → FredPret]

> There's a nice synergy between using Mac and Linux - many of the same scripts, commands, and concepts work identically.

I switched to a Mac a few months ago from Windows and I kinda hate the small differences with Linux, I like WSL much better. On top of my head,

- No systemd

- No native docker

- No valgrind (there is https://github.com/LouisBrunner/valgrind-macos though)

I basically have to install a Linux VM on Mac just for this, at which point WSL on Windows is a much better tradeoff IMO.

[FredPret → magnio]

I'm not super familiar with WSL; does it allow you full access to all your files, or is it a fenced-off environment?

On my Mac I have various cronjobs and scripts running that work copy-paste the same as on a real server. I even have Nginx serving static files for local development!

[yreg → FredPret]

Easily. Your Windows C: drive is in /mnt/c in WSL.

And your WSL root (/) is in e.g. \\wsl.localhost\Ubuntu on Windows.

[FredPret → yreg]

It’s too late for me, but that’s quite nice actually.