erdtree VS fish-shell

The most substantial project that I have to show for my knowledge of the lower level topics is this project I work on in my spare-time called erdtree and I'm really banking on that to stand-in as "experience" in the absence of professional systems experience.

I'm working on this little project called erdtree and could use a bit of help adding information about file owners and permissions for the windows build if you're interested. No worries if not :)

I actually do put my main function in the middle

User feedback really helps drive erdtree's development so happy to accept input if you have any! And yeah et became erd because of name clashes with a lot of other existing packages.

I'm a self-taught developer working professionally as a director of engineering who writes Rust on weekends. I've been using Rust now for a little over 2 years and am the author and maintainer of this little command-line tool called erdtree. Before I was a programmer I did extensive tutoring in various subjects like organic chemistry, biochemistry, physics, calculus, etc..

Took a healthy break from this little open-source project I've been iterating on.. ready to get back to it this weekend :]

I personally use erdtree, it even uses icons to differentiate various kinds of files

Here’s a project that I work on in my spare time. I initially worked on a very bare bones version on a 6-hour plan ride back in spring of 2022 because I was bored and wanted to work on something challenging without the need for internet. After two days I posted a naive version onto GitHub and after like 6 months it got around 100 stars on GitHub so I then decided to give it special attention in January of this year and have been iterating on it since.

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512