3
Rust Port for Fish Shell is Almost Ready for a Beta Release (news.itsfoss.com)
submitted 2 years ago by to c/rust@programming.dev
8 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 0 points 2 years ago (1 child)

I still don't know what the fuck they mean by "make it available for servers".

They said that in the earlier post too and I have no clue how they came up with that.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    They said on a linked post:

    Make fish available on servers that run old LTS distros Making it easy to build and run

    Which suggests to me they are using features from newer versions of libraries then exist for older LTS distos. Making it hard to compile and run on them. Most of rust libraries are statically compiled so that is not an big issue for rust. Though this is just speculation on my part.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago* (1 child)

    There is nothing specific in the rust port that makes fish more available for servers or LTS distros.

    Before, you would have had to get a C++11 compiler (which used to be a bit of a PITA until 2020 or so), now you need to get rust 1.70 (which isn't terrible given rustup exists).

    I see they're taking it from this comment, which says

    Fish should be available on servers, which run old LTS distros - this means we build our own packages for a variety of them.

    Which is something that fish has always done - you can go to https://fishshell.com/ and get packages for Ubuntu, Debian, OpenSUSE and CentOS - all server distros, and these packages are built by the fish developers, not the distros.

    That quote comes from the "Setting The Stage" section of the comment, which describes the status quo. This is about explaining what fish does and needs from a new language, not about something that fish wants to achieve by switching the language.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago* (last edited 2 years ago) (1 child)

    There is nothing specific in the rust port that makes fish more available for servers or LTS distros.

    Being written in Rust does improve availability, because by default Rust statically links against everything except libc, and you can opt out of that if necessary. So there is inherently no need to build separate dependency packages for each distro, unless you use a Rust crate that specifically links to a C or C++ library.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (last edited 2 years ago)

    fish links against pcre2, which is a C library (via the pcre2 crate).

    (it used to also link against ncurses, now it uses the terminfo crate instead, which just reads the terminfo database in rust)

    Of course there is a way to make fish distributable as almost a single file (https://github.com/fish-shell/fish-shell/pull/10367), which rust does make easier (rust-embed is frickin' cool), but these sorts of shenanigans would also be possible with C++ and aren't really a big driver of the rust port. It's more that cargo install would try to install it like that and so why not make that work?

    Really, my issue here is that the article makes "making fish available on servers" this huge deal when fish has always been available on servers?

  • permalink
  • fedilink
  • source
  • parent