Hate to break it to ya, buuuut:

• Lester Townes “Bob” Hope (né Leslie Townes Hope; May 29, 1903 – July 27, 2003)
• John R. Cash (born J. R. Cash; February 26, 1932 – September 12, 2003)
• Steven Paul Jobs (February 24, 1955 – October 5, 2011)

The last of these died 15 years ago.

OwO

In the world at large? Yeah. But the story you’ll hear cited most often on tumblr is the pregnant Loki one, because of the genderfuckery / queer interpretation.

I mean they did use the single most well-known norse myth fact on tumblr, so

What do you think “Nazi punks fuck off” was for?

It’s sourced in CachyOS’ default fish config.

Which is already pretty awkward - fish has a way to add extra files to source at startup, they’d just have to install it in the correct directory.

(but then this config has a bunch of issues, including breaking the default history function and adding a separate fish_profile file for no good reason, …)

The website has about 50 lines of non-generated javascript. Even counting the generated JS, fish-site is 96.5% html.

(either way, setting a “main repo” here seems to be table stakes and does not fill me with confidence about OpenHub)

Openhub also says it’s “mostly written in javascript”.

But in all seriousness: The port wasn’t the greatest time for new contributors, because there wasn’t a lot of feature work or cleanup happening.

So I’d expect more now.

There is the point you can make, which is that you can more easily create self-contained statically linked binaries (tho fish needs more than what cargo itself can provide here because it ships a ton of data files, see https://github.com/fish-shell/fish-shell/pull/10367),

and then there’s what this site keeps claiming from a misreading of a comment I made when the port just got started, which is that fish is now “available on servers”. Which is just wrong, it’s always been available on servers and it’s been easy to install a new fish on LTS distros for users for ages.

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?

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.

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.