Hacker News Reader

Comment by matt_wulfeck | Hacker News Reader

Tools like curl being available is one of the reasons I fell in love with development on Mac. I hope Apple takes note and ships curl (and other coreutils for that matter) in a way that continues to be developer friendly.

View on HN

Note that all GNU tools on Mac OS are the last GPLv2 versions. Their version of bash, for example, was ten years old the last time I checked. In contrast, most GNU/Linux distributions do provide up-to-date tools out of the box.

In addition, Apple makes it difficult to modify or upgrade installed software, even when is it vulnerable. The default installation of git in OS X once had a remote code execution vulnerability that could not be patched by users: http://rachelbythebay.com/w/2016/04/17/unprotected/

On macOS since 10.11, there is `nscurl`, which is a curl-like on NSURLSession where HTTP/2 is available.

Interesting. It doesn't have a man page, the help output gives no background info and there's very little information online. I'm curious to find out more about this tool.

    nscurl -h

gives some useful info

Any reason you're not using homebrew or another package manager to have the latest version of curl built against whatever SSL library you want?

While installing a new version of curl via homebrew is great, I think that this is just sidestepping a bigger issue.

Take vim for instance. The reason why I know vi is because it's everywhere. I know full well that any unix machine I log into will have it available to me if I need to edit a file. Now imagine that OSX released a new file structure, and the native vi installation couldn't read those files. Yea I could install a newer version of vi, but it means that I can't use any mac to fix something if I really need to. It means there's an inconsistency in the very basic command line functionality that I trust and rely on to be there.

Things like curl, vi, sed, etc are my fallback tools. If my reserve chute doesn't work, problems will arise at some point.

>Take vim for instance. The reason why I know vi is because it's everywhere. I know full well that any unix machine I log into will have it available to me if I need to edit a file. Now imagine that OSX released a new file structure, and the native vi installation couldn't read those files. Yea I could install a newer version of vi, but it means that I can't use any mac to fix something if I really need to.

So? Macs are used as personal machines, not interchangeable accounts on servers.

Many people do use them as interchangeable machines. And even if yours is personal, there is value in a coworker being able to show you e.g. what change to make to a config file.

>Many people do use them as interchangeable machines.

For small values of "many".

Reply on news.ycombinator.com