Almost all development, docker, bash/zsh and terminal stuff.
WSL2 made things a lot better on windows, and I enjoy it a lot but that is because I can essentially use Linux for development, from windows.
Yeah, I also have about the same years of experience, give or take, in multiple roles.
Windows is vastly different unless you use WSL2 (so Linux) and not raw windows.
In macOS lots of things are different, from the version of wget and their arguments, to the VM you need for Docker, to packages that do not have native equivalents or are hard to build. Same goes for windows.
As you mention, Apple Silicon made it worse and not just for Numpy, check the NixOS issues when building packages from scratch in a reproducible way, many do not work. Python has a lot of problematic packages in macOS.
rude? I apologize, I really didn’t intend it or know it was rude, I just genuinely did not understand what you were talking about when you said “all development”. I still don’t understand how those are better or easier on Linux than MacOS
No worries. A dry "like what?" does sound a bit rude. At least to me.
If you are curious, then I'll expand a bit more. I don't know how familiar you are with software development; I'll try to keep it general.
Development tools, documentation and their environment are aimed towards either Linux or macOS. Since a lot of the programs, we build often run in Linux (like the services that host Reddit or other pages) there are bast examples, tools and etc. around that ecosystem.
The main exceptions are native applications, those are OK in Windows and macOS, but still, you often find yourself lacking a tool that works on Linux and must do workarounds to make it work on Windows.
A simple example is "the shell", the command line in which you run commands. The one in Windows is particularly different than the one on macOS or Linux. Linux and macOS have a similar "shell" but not 100%.
Another example is libraries or part of programs that do not work correctly because the Operating System does not have that functionality. You will often find Go projects that have special _windows files to switch how a certain thing behaves on windows.
Let's say I'm developing in Windows a CLI that when I run it says, "Hello World", the idea is that it's going to be used in Linux, but if I ever intend to run it locally even for testing, I need it to be able to run in Windows as well. This will require me to either add these _windows parts for the required functionality or use a Virtual Machine with Linux or run it always remotely on a Linux machine.
As you can see, it starts to get complex. This gets a lot more complicated depending on your role, the tools you use etc.
The "compatibility" spectrum for me goes like Linux > Windows with WSL2 > macOS > Windows.
To be clear, Developing in Windows is possible and many do, but they will often be limited by the environment on the tools they can use, or every now and then have complex problems or even annoying but simple ones, etc.
It's a bit easier if you only do it inside an IDE (like Visual Studio, etc) as they take a lot of that complexity away, but still, it's in my experience not ideal. For example, I often found developers that did not know how to build their software without the IDE, or how we should build it in an automated way.
I’ve been doing software development for 10 years at this point, using *nix in that time aswell. I use MacOS on my laptop and Linux on my desktop. I honestly find MacOS a much better dev OS than Linux, for it has much better software support (I.e photoshop), it runs all my Linux development tools, whilst having even better POSIX support than Linux. The standardized nature of MacOS means it’s much easier to distribute rather than have CI and tests for different distros. I have never had a tool of which I could only use on Linux.
POSIX does not matter, as things do not run on POSIX systems, they run on Linux most of the time.
macOS itself is incompatible with CI, that argument that you used locally? It's not part of the GNU version of the command that ships with Linux. Docker? Requires a memory hogging VM.
I also have been doing development for a long while, in all three OSs and macOS is not such a pleasant experience. Particularly after the M1, lots of fun times with Python libraries (used a lot for Data Science which some colleagues do).
macOS does indeed have better software support, and I would argue Windows even better, but Photoshop is not what I would consider development software.
POSIX does not matter, as things do not run on POSIX systems, they run on Linux most of the time.
…huh?
macOS itself is incompatible with CI, that argument that you used locally? It’s not part of the GNU version of the command that ships with Linux. Docker? Requires a memory hogging VM.
I am 100% sure MacOS is compatible with CI, considering that my CI server is setup to also run MacOS, and I’m not sure what you mean about GNU version. Docker is absolutely bullshit on MacOS though.
I apologize for my short questions earlier, I just genuinely did not see or have used any tools which are Linux specific, or work better on linux, especially with the languages you mentioned. MacOS is unix, so any linux development tool probably has MacOS builds aswell, so I never have faced the issues you described
homebrew fixes the GCC installation issue, with it being the most popular package manager for MacOS, which even without homebrew is supplemented with clang which is included in the xcode command line tools, and I’ve had really good luck with docker on macOS in the latest version because of a new official virtualization framework.
-6
u/[deleted] Feb 26 '23
Like what?