5 ms·
What exactly does your development workflow look like where Linux was so much better than MacOS?
by fastball 9y ago
What exactly does your development workflow look like where Linux was so much better than MacOS?
- garmaine 9y agoWhat was the workflow in which windows was better than anything UNIX based....
- ratsimihah 9y agoI’m missing the logic as well. Linux > Windows > macOS?
- pjmlp 9y agoDesktop software development, graphical debugging tools. The only UNIX based that tops it is macOS.
- garmaine 9y agoBut Linux is better for that?
- pjmlp 9y agoNot all all, Linux is the culture of command line, where people improving UI/UX on GNOME/KDE always get bashed as taking the power away doing irrelevant work. There is not a single cohesive stack of desktop technologies, what macOS calls Kits, Android frameworks, Windows UWP and such. Something like Glade still fails short of what XCode or VS Blend are capable of. Sure there is something like Qt QML designer, but that isn't Linux specific anyway.
- garmaine 9y agoYou are missing context. Grandparent was claiming that Linux was the best OS he’d used for development (fair enough), but that he’d rather have Windows over macOS otherwise. That part I was hoping for clarification on.
- electricslpnsld 9y agoNot OP, but the LLVM toolchain provided by Apple is a bit clunky and missing features relative to what you get from a typical Linux distro.
- chuckdries 9y agoMacs ship with outdated versions of common bash commands and tools as well. Homebrew goes a long way to fixing this for me.
- Lio 9y agoI have the same problem on Ubuntu LTS distributions. Eg the ancient version of git in 16.04LTS. You can fix that of course but homebrew does the same job on macOS. Roll on 18.04LTS.
- figgis 9y agoThe most enjoyable and productive dev workstations I have used/setup have all used rolling release distro's for this exact reason. It does have the overhead of requiring you actually understand (or know how to google) your system/packages that you use though.
- Lio 9y agoIt's not just understanding the packages. When I upgraded from 16.04LTS to 17.10 I had to relearn how to compile the kernel because my laptop would no longer boot. Wasn't that hard to do in the end but it's not something I've done for many, many years and doesn't fill me with confidence.
- sitkack 9y agoHomebrew exists on Linux. I like running LTS distros because they just work. For newer per-project exceptions, I put everything into a container (again layered on LTS), it is esp nice for things like specific versions of LLVM which I wouldn't want to pollute my base machine with. My peronal userland gets shipped via, cargo, go, pip, npm, etc. https://github.com/Linuxbrew/brew https://github.com/Linuxbrew/brew
- zeveb 9y agoStumpWM & a full GNU userland just like the machines we deploy on are killer.
- jcfrei 9y agoApple frequently introduces changes to its OS that caters to the average user without any hindsight for developers. A good example I had to deal with; I wanted to change the port the SSH daemon listens on. With El Capitan and future versions you have to temporarily disable SIP (System Integrity Protection) - which requires two reboots - in order to make the change to the ssh.plist file. As you can see it's a common problem: https://apple.stackexchange.com/a/208481 https://apple.stackexchange.com/a/208481 It's lots of little things like this that require extra effort on OSX but which are straightforward on a decent Linux distro.
- voltagex_ 9y agoIs there anything stopping you using a separate sshd to run on a different port? Or using one from homebrew instead of Apple's bundled one?
- no_wizard 9y agoFlatly, This isn't true. I can still go into /etc/ssh sudo vim sshd_config, can my values, and they stick. Just to test it, I did it right now, and I'm running 10.13.4, for what its worth. What exactly was the issue with changing the sshd config? This isn't a SIP protected directory, which is the only thing that would prevent such a move. Perhaps the requirement of sudo? I feel like most linux distros force that in the /etc directory too.
- jcfrei 9y agoChanging /etc/ssh/sshd_config was my first attempt as well. But since this is OSX things are a little different, see here: https://serverfault.com/a/67616/ https://serverfault.com/a/67616/
- fastball 9y agothis security feature that is great for the vast majority of Apple's user's isn't convenient for me. Luckily, Apple shipped SIP with the option to disable it, and it's not hard. So you can disable it once and then you never need to deal with issues like that again. It's weird because it sounds like you want the protection of SIP without the inconvenience of SIP, but that's never been possible with pretty much any security measure ever -- more safety means less convenience. That being said, to me Apple has actually been the best when it comest to safety/convenience ratio. Linux distros don't even have the option of SIP or something similar, so I can't say I find your argument compelling.