4 ms·
I get an awful lot of mileage out of the XCode command line tools. Most of the things you need to emulate a CI pipeline locally are there, though the exceptions
by hinkley 4y ago
I get an awful lot of mileage out of the XCode command line tools. Most of the things you need to emulate a CI pipeline locally are there, though the exceptions can occasionally be a bit of a problem.
- heywoodlh 4y agoWhat tools do you use/find essential that get installed with XCode's command line tools? My experience with XCode's command line tools is pretty much just installing them for Homebrew. I don't think I've taken time to actually dig into the installed tools -- so I'd love to hear what tools increase your mileage! :)
- rtpg 4y agoThe insistence on having to install the xcode command line tools (hello "be at 99% installed for 10 hours" bug I have had over 5 different machines") is very annoyin. But I've found that brew has been a major mess as well. Nothing like coming in on a Monday and having to debug 10 coworker's machines cuz suddenly python and postgres were silently upgraded (or some random shared lib was upgraded). "Just use Docker" is also a PITA cuz of the abysmal file system performance stuff... I just want to run software! Or rather, I want my coworkers who might not be as well versed in system software to be able to have working systems. All that being said, it's undeniable that I can daily drive Linux thanks to Mac stuff existing.
- drunkpotato 4y agoI've found that asdf has replaced a lot of my brew installs. It's great to be able to pin tool dependencies per project. I used, and liked, brew for a long time, but my tooling these days is almost entirely MacPorts, asdf-vm, and Docker + docker-compose (I'm also intrigued by podman).
- hinkley 4y agoxcode is enough to make nvm, asdf work. With only a very few exceptions I've found it to be enough to run javascript frontends, and backends of javascript, Ruby, Node...