sometimes i have to chuckle when reading headlines on here.
if someone has no IT knowledge, or maybe just doesn't know rust or fish, "Rust Port for Fish Shell" is probably undecipherable. Doesn't even sound like something related to IT.
since when do fish have shells and why is the port rusty, and why do these fish even need a port?!?
You can't imagine how hard i feel your words. And to add on that... I'm not a native speaker of english.
Many years ago i was starting my learning journey with kubernetes, and all names had a nautical theme. I was learning about helm charts... and of course, a chart for me was something like a graph, with x and y axis, maybe some z axis... histograms, that kind of things. So the word "chart" didn't make sense when talking about release management, text files and `text/template` go code.
I had to casually stumble upon the concept of nautical charts for things to start making sense...
Our industry has this kind of clownish traits some times.
I get the value of Rust, if not the extreme enthusiasm surrounding it sometimes.
With regard to a larger project like this, I'm more interested in is the buy-in of the major contributors of of the fish shell. Are they all in on it? Is it just decided that leaving a few behind and losing their deep knowledge is worth it?
All of these "Rewrite in xyz" strike me as impractical, but it's never my place to tell someone to stop the impractical.
14 comments
[ 2.4 ms ] story [ 43.5 ms ] thread/s
if someone has no IT knowledge, or maybe just doesn't know rust or fish, "Rust Port for Fish Shell" is probably undecipherable. Doesn't even sound like something related to IT.
since when do fish have shells and why is the port rusty, and why do these fish even need a port?!?
Many years ago i was starting my learning journey with kubernetes, and all names had a nautical theme. I was learning about helm charts... and of course, a chart for me was something like a graph, with x and y axis, maybe some z axis... histograms, that kind of things. So the word "chart" didn't make sense when talking about release management, text files and `text/template` go code.
I had to casually stumble upon the concept of nautical charts for things to start making sense...
Our industry has this kind of clownish traits some times.
E: Here it is https://news.ycombinator.com/item?id=41098931
I stared at it, clicked on it, scrolled through and remained totally confused until I noticed the repo name.
With regard to a larger project like this, I'm more interested in is the buy-in of the major contributors of of the fish shell. Are they all in on it? Is it just decided that leaving a few behind and losing their deep knowledge is worth it?
All of these "Rewrite in xyz" strike me as impractical, but it's never my place to tell someone to stop the impractical.