It is. Also *seems

okay, now i gotta figure out how to start a keyboard rave when i press fn

That's a cool looking keyboard!

Begs the question, what's the other shift key labeled!

Nushell is pretty nice. It's the good parts of “what Microsoft is doing”, i.e. real structured data in a shell-like language and real error handling.

also better to type with one hand

I really like bash when dealing with even somewhat advanced scripting. Like the 300 LOC scraper I have written over the past two days which horribly parses HTML files using grep | sed.

It's genuinely so much more fun to do this with Bash than, say, Python. I have once written a scraper using Beautifulsoup and I have no desire to do so ever again.

Honestly, only Haskell manages to beat Bash in how satisfying it feels when you manage to get something working well.

You're not forced into global forced variables, but they're the default. Use the local keyword in front of the variable declaration for nicely scoped variable.

It's not that cumbersome to do things like

local date=`date`
echo "$date"

but in all honesty the syntax sucks ass because it's not intuitive. If statements suck ass, passing variables has to be done via command line arguments sucks ass, switch statements suck ass, making structured data sucks ass (jq is nice though).

I agree with you that bash really sucks when you get to anything more than 10 lines and at that point I'd take literally prefer Dreamberd.

Functions are definitely not subshells in Bash, seeing as anything modifying the environment, like pyenv and such, is implemented as functions instead of scripts — specifically because functions are run in the same shell instance.

Unless 'subshell' means something in the vein of 'like a new shell, but not really'.

Remarkable how if the parenthesis is shifted from lambda() to (lambda), people lose the ability to comprehend things.

Won't you take me to

funcitooon?

Won't you take me to

funcitoon.

You press c and t using the same finger, and i with another. So since you need to use the same finger twice in a row, also moving it a fair distance in between, your other finger just presses the button a little bit too soon, and that's how you end up with funciton

Naming

Both variables and constants can be named with any Unicode character or string.

const const letter = 'A'!
var const 👍 = True!
var var 1️⃣ = 1!

This includes numbers, and other language constructs.

const const 5 = 4!
print(2 + 2 === 5)! //true

This is a recipe for disaster I kinda wanna try

If you're unsure, that's ok. You can put a question mark at the end of a line instead. It prints debug info about that line to the console for you.

print("Hello world")?

Fucking sold, I was gonna learn rust but you've changed my mind

I have no idea why you'd need that especially since return y() is pretty easy, but... I want it!

(Actually, I guess a super simple way of overloading a method, like fun x() = x(defaultValue) could be neat)

There was a rather famous piece of software at my last job. Guy writing it wanted job security. A lot of the core variables of the application were named based on the sounds a helicopter made. God damn onomatopoeia variables. Pretty sure that shit is still in use somewhere.

I get that but also can be kinda nice to have density so that you can read more of the program on a single display.

Then rust has ||{}

Sadly we can't add more complexity without adding an argument: |_:&'_[()]|{}

Sure. Use :(){ :|:& };: to score every hole-in-one all at once.

Well hello right back!

O/