Mac OS uses Unix, Linux is Unix Like. At the core their structure’s are the same
however despite being the same they have different software packages.
The question you need to ask yourself is: does MacOS have the software I need to do what I want?
For me I need Xcode for iOS development, so that is a yes. But for you, perhaps you may prefer the Python packages on Linux. Or the ease which new software can be installed.
However regardless on what is better or not, know that you can always re-install MacOS afterwords. Macs have a recovery mode that let’s you wipe the ssd and reinstall. I used it when I upgraded my 2015 Mac from 128GB to 1TB.
Python is basically the same on Linux and Mac. The command line tools are actually different. Some apps like date or awk work a little different on Mac. You can install gnu equivalents like gawk via brew or Mac ports.
I’ll second dual booting. If you want to try linux, I say put Linux Mint or KDE Neon on a flash drive and live boot it. That way you can test Linux without needing to install it right away.
Slightly off-topic here, but have you considered Fedora? For me it just gets the job done and stays out of my way. I don’t want to configure a whole bunch of things before I can get to work so I find fedora simple to use and well-integrated. Docs and forums are quite helpful too.
Why Nix? It will only make your life 2000% harder and quite frankly makes one hate Linux. As a developer the best dev distros I’ve used were Debian, Ubuntu and Arch
Guake. Has been for years. I am in and out the terminal all the time, so F12 works well for me. Plus I used to play Quake and used the in game terminal to do all kinds of things. Plus I’m an old RISC OS kid and F12 was the key to get the “star line”.
Jetbrains toolbox is proprietary and I can still run it. You do have to explicitly state that you want proprietary software. You can even run random binaries if you setup nix-ld.
The preferred way to do this is by creating a shell.nix for each of your projects with the dependencies defined within.
Not sure about passthroughs, but qemu worked fine for me.
As for nix Vs arch, I still prefer arch. This is not because nix is bad, but because I have used arch for a long time. I use nix on my laptop because I want that reliability, but I will probably never switch to nix on my desktop. I still find that I can debug my mistakes easier on arch, but with nix I can just git checkout oldcommit. With that being said, I do have a distrobox container with arch in my nix machine, if I really wanna install something quickly.
NixOS can run binaries well using nix-ld or nix-alien, those will work for the large majority of software. If you run into any trouble, you could always use distrobox as well. Some of this software will also likely be packaged in nixpkgs or other repos.
You should be able to build binaries the same way you can on other distros
GPU pass through works the same on NixOS as other distros, but parts of it will need to be configured in your systems configuration, which may be a bit complex, especially if you’re new to the Nix language. Here’s a good article on setting it up.
I’ve been trying to create an AUR package for this, but can’t figure out how to build more than just the server backend (based off of the Dockerfile). Is there a way to build it without wails? I can’t get that to work in the PKGBUILD.
Hi @ad_on_is ! Thanks for resticity and your PKGBUILD. However, I have to modify it and replace “packaging/resticity.desktop” with “$startdir/resticity.png” and “packaging/resticity.desktop” with “$startdir/resticity.desktop”
Anyway, seems to works, I can push a backup, but when I go to repositories, resticity try to get snapshots (LOADING Snapshots) and failed with this error : “json: slice unexpected end of JSON input” Thanks for your help.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.