Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.

4recommend
0warn against
Nov 14, 2025first mention
Jul 17, 2026latest mention
Nov 25 – Oct 26
Used forshell scriptingshellplan 9 shelllearning shell design

Why people recommend it

“I solve this problem by using a shell that doesn't do that [1].”

“it is a worthwhile read for anybody interested in shells”

Show 3 more

“rc [1] replaced it with a far more telling”

“there's rc, awk and aux/* helper tools which can do tons of stuff Perl does”

“avoids semicolons that Bourne requires in odd places”

Caveats and dissent

No one in these comments warned against it.

Often compared with

From the makers not counted in the ranking

“Using it already (the granular branch) but it's far from stabilized”

All comments 8

“I used the rc shell from plan9 for quite a while”

“I solve this problem by using a shell that doesn't do that [1].”

“it is a worthwhile read for anybody interested in shells”

“rc [1] replaced it with a far more telling”

“there's rc, awk and aux/* helper tools which can do tons of stuff Perl does”

“avoids semicolons that Bourne requires in odd places”

> I’m not saying it’s wrong to have a preference for smaller languages, I just haven’t seen anything in my career to indicate that smaller languages outperform when it comes to faster delivery or less bugs. I can imagine myself grappling with a language feature unobvious to me and eventually getting distracted. Sure, there is a lot of things unobvious to me but Go is not one of them and it influenced the whole enviro

Threads where it came up

Data: rc.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help