7 ms·

> But, I'm kinda baffled why anyone would volunteer to provide free labor to one of the largest and most profitable companies in the world. YES! MacOS users do

> But, I'm kinda baffled why anyone would volunteer to provide free labor to one of the largest and most profitable companies in the world. YES! MacOS users don't need to document macOS as a volunteer project, they need to demand Apple to give them their money's worth.

fnord123 9y ago
And yet Apple does not contribute to homebrew at all. The one project that makes osx usable for developers.
- wbl 9y ago
  They did contribute to Macports which does the same.
- deleted 9y ago
  [deleted]
- krrrh 9y ago
  iirc, they actually contacted Max Howell (creator of homebrew) and got his input on how to make command line tools work better for developers and homebrew specifically.
  - herbst 9y ago
    Assuming this happened and lead to anything it is still far from actually supporting it.
    - Gaelan 9y ago
      IIRC Max now works at Apple and is responsible for Swift's package manager.
      - shenaor 9y ago
        I think he left sometime last year https://changelog.com/podcast/232 https://changelog.com/podcast/232 they start talking about his departure from Apple at 55 min and 26s, unless he went back recently
        Gaelan 9y ago
        Ah.
- pjmlp 9y ago
  I used OS X a few times for iOS development, never used homebrew. Am I not a developer?
  - khedoros1 9y ago
    Maybe you had different requirements than other developers. Or maybe you've got a lower bar for considering something "usable".
    - pjmlp 9y ago
      My requirements were those that any OS X and iOS developer have, which don't require UNIX CLI rather XCode tooling, and are happy to use any UNIX certified POSIX system for the occasional CLI automation of OS X and iOS development. Now those that bought OS X as a pretty alternative to GNU/Linux and *BSD, for development that should actually be done on those systems, might miss something like homebrew. Apparently only those are developers on HN speak.
      - deleted 9y ago
        [deleted]
      - khedoros1 9y ago
        Interesting definitions. Theirs excludes you as an OSX developer, and yours excludes them as OSX developers. How about: Your requirements weren't those of "any OS X and iOS developer", unless you apply a "no true Scotsman" argument. Similarly, a nicer CLI environment is only applicable to some styles of dev on OSX.
        deleted 9y ago
        [deleted]
        pjmlp 9y ago
        OS X is a certified UNIX, no need for external tooling.

fnord123 9y ago

And yet Apple does not contribute to homebrew at all. The one project that makes osx usable for developers.

wbl 9y ago
They did contribute to Macports which does the same.
deleted 9y ago
[deleted]
krrrh 9y ago
iirc, they actually contacted Max Howell (creator of homebrew) and got his input on how to make command line tools work better for developers and homebrew specifically.
- herbst 9y ago
  Assuming this happened and lead to anything it is still far from actually supporting it.
  - Gaelan 9y ago
    IIRC Max now works at Apple and is responsible for Swift's package manager.
    - shenaor 9y ago
      I think he left sometime last year https://changelog.com/podcast/232 https://changelog.com/podcast/232 they start talking about his departure from Apple at 55 min and 26s, unless he went back recently
      - Gaelan 9y ago
        Ah.
pjmlp 9y ago
I used OS X a few times for iOS development, never used homebrew. Am I not a developer?
- khedoros1 9y ago
  Maybe you had different requirements than other developers. Or maybe you've got a lower bar for considering something "usable".
  - pjmlp 9y ago
    My requirements were those that any OS X and iOS developer have, which don't require UNIX CLI rather XCode tooling, and are happy to use any UNIX certified POSIX system for the occasional CLI automation of OS X and iOS development. Now those that bought OS X as a pretty alternative to GNU/Linux and *BSD, for development that should actually be done on those systems, might miss something like homebrew. Apparently only those are developers on HN speak.
    - deleted 9y ago
      [deleted]
    - khedoros1 9y ago
      Interesting definitions. Theirs excludes you as an OSX developer, and yours excludes them as OSX developers. How about: Your requirements weren't those of "any OS X and iOS developer", unless you apply a "no true Scotsman" argument. Similarly, a nicer CLI environment is only applicable to some styles of dev on OSX.
      - deleted 9y ago
        [deleted]
      - pjmlp 9y ago
        OS X is a certified UNIX, no need for external tooling.