6 ms·

One of the things that drew me to Macs as I started to learn programming in '05 was that I could simply open any macbook and type python/ruby/perl and write som

One of the things that drew me to Macs as I started to learn programming in '05 was that I could simply open any macbook and type python/ruby/perl and write some code.

Fnoord 7y ago
Different time. Now you got Homebrew
- pdpi 7y ago
  Which installs itself based on the system Ruby. Will be interesting to see how that plays out.
  - Fnoord 7y ago
    They just pack a statically compiled Ruby interpreter with Homebrew. Not very complex or novel. Disadvantage: install becomes more bloated (larger size).
    - pdpi 7y ago
      Sure, it’s not a hard engineering challenge. However, installation instructions right now are as simple as “run this one-liner on your terminal”. That’ll have to materially change.
      - Fnoord 7y ago
        > Sure, it’s not a hard engineering challenge. However, installation instructions right now are as simple as “run this one-liner on your terminal”. That’ll have to materially change. It could just as well still remain a one-liner. Every system Homebrew is installed on has Bash installed (not the latest, but still). Instead of > /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" https://raw.githubusercontent.com/Homebrew/install/master/in... It could become > curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install https://raw.githubusercontent.com/Homebrew/install/master/in... | bash With the install script containing a payload containing the current Ruby script plus a Ruby interpreter. Still a "one liner".
        toyg 7y ago
        > Every system Homebrew is installed on has Bash installed Ironically, they are also moving from bash to zsh for default shell. Again not an unsurmontable challenge (just make sure the bang is correct in your scripts, bash will likely still be around somewhere in macOS for the foreseeable future) but another little hurdle to mind.
        Fnoord 7y ago
        Doesn't surprise me given they dislike GPLv3 and Zsh is MIT. Personally I try to use #!/bin/sh as much as possible, and Fish as my default shell.
        holtalanm 7y ago
        upvoted for fish
        Sean1708 7y ago
        As far as I'm aware they're not changing anything about which shells are installed or which executable /bin/sh points to they're just changing the default login shell for a new user, so nothing should have to change about the scripts that are (or have been) written.
      - butteroverflow 7y ago
        Take a look at the installation instructions for the Rust compiler. https://rustup.rs/ https://rustup.rs/
  - nbaksalyar 7y ago
    Like it works now with older versions of macOS and on Linux: it downloads a Ruby binary when it's not available on the host system.
musicale 7y ago
But you have to download Xcode if you want a C compiler! On the up side though, clang has made the C/C++/ObjC world a much better place.

One of the things that drew me to Macs as I started to learn programming in '05 was that I could simply open any macbook and type python/ruby/perl and write some code.

Fnoord 7y ago

Different time. Now you got Homebrew

pdpi 7y ago
Which installs itself based on the system Ruby. Will be interesting to see how that plays out.
- Fnoord 7y ago
  They just pack a statically compiled Ruby interpreter with Homebrew. Not very complex or novel. Disadvantage: install becomes more bloated (larger size).
  - pdpi 7y ago
    Sure, it’s not a hard engineering challenge. However, installation instructions right now are as simple as “run this one-liner on your terminal”. That’ll have to materially change.
    - Fnoord 7y ago
      > Sure, it’s not a hard engineering challenge. However, installation instructions right now are as simple as “run this one-liner on your terminal”. That’ll have to materially change. It could just as well still remain a one-liner. Every system Homebrew is installed on has Bash installed (not the latest, but still). Instead of > /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" https://raw.githubusercontent.com/Homebrew/install/master/in... It could become > curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install https://raw.githubusercontent.com/Homebrew/install/master/in... | bash With the install script containing a payload containing the current Ruby script plus a Ruby interpreter. Still a "one liner".
      - toyg 7y ago
        > Every system Homebrew is installed on has Bash installed Ironically, they are also moving from bash to zsh for default shell. Again not an unsurmontable challenge (just make sure the bang is correct in your scripts, bash will likely still be around somewhere in macOS for the foreseeable future) but another little hurdle to mind.
        Fnoord 7y ago
        Doesn't surprise me given they dislike GPLv3 and Zsh is MIT. Personally I try to use #!/bin/sh as much as possible, and Fish as my default shell.
        holtalanm 7y ago
        upvoted for fish
        Sean1708 7y ago
        As far as I'm aware they're not changing anything about which shells are installed or which executable /bin/sh points to they're just changing the default login shell for a new user, so nothing should have to change about the scripts that are (or have been) written.
    - butteroverflow 7y ago
      Take a look at the installation instructions for the Rust compiler. https://rustup.rs/ https://rustup.rs/
- nbaksalyar 7y ago
  Like it works now with older versions of macOS and on Linux: it downloads a Ruby binary when it's not available on the host system.

musicale 7y ago

But you have to download Xcode if you want a C compiler! On the up side though, clang has made the C/C++/ObjC world a much better place.