>>106537951
What if powershell but freetarded and with a side of rust.

>>106537951
Well, imagine having to type
>ls | sort-by size | reverse
instead of
>ls -lhS
This will, over time, increase your typing skills

>>106538013
former literally says what it does, latter is some shit you can't tell what it does without looking up every fucking letter in the manpage first. Former >>> latter any day

Memorization of arbitrary symbols is a happy coincidence from repetition, it should never be the requirement

>>106537951
no

>>106537983
Why though

>>106538293
Our brains are built for memorization of arbitrary symbols in the name of efficiency. That's why natural language works the way it does.
If you actually use the command line on a daily basis, memorization is inevitable and this is not an issue. Your argument just further confirms that rustoids don't actually like CLI and only pretend use it for esthetics.

Now go ahead and show me an example of nushell that's actually useful.

>>106537951
did anyone tell them that 'nu' has a connotation of being effete

>>106538482
stop noticing things

>>106538335
it's nu

>>106537951
Buy an ad

>>106537951
i write rust code daily, and i like the premise of nu which i came across from its inception. beyond the main features/ideas of the shell, things like native ingesting/egesting of json data for example makes great practical sense.
having said all that, i will probably be stuck with zsh forever. i'm too lazy (and maybe old) to change shells at this point.

>>106539142
K, but that was already done PowerShell

File: 1753229742597483.gif (1.02 MB, 3000x3000)

1.02 MB GIF

>i write rust code daily

>>106537951
Dickless retard. Stop spamming your gay shit.

>>106537951
>can't run bash scripts
into the trash it goes

>>106537951
>>106539756
let me explain what i mean,

no one will abandon decades old bash to use some "nushell".
the only reason powershell got big was because cmd was so fucking quirky and antiquated.

bash is also a little old in the tooth but its still usable and it just werks.
yes, you have some differences between different shell implementations but they all agree on some sameness. its relatively easy to port a script from one shell to the other while most scripts don't need adaption at all.

but whatever, time will tell.
but seriously, having no compatibility with bash is not cool

and even comparing different shells like zsh or ksh, no one seems to care that zsh has floating point number support. in fact, no one gives a fuck.

>>106539924
1. Backwards compatibility is the root of all evil.
2. PowerShell got big due to system administrators being able to automate all parts of Windows and AD using it. It got bigger following PS Core as a DevOps tools for Azure.

There's very few programmaers that care about PowerShell, even on Windows, as anything more than a place to dump commands in. The amount of people using PowerShell as a login shell on Linux is a rounding error.

>>106538013
>filtered by prefixing commands with ^
>not using eza anyway
i don't even use nu. and i cleared that /g/eet "filter".
>>106539335
90%+ of people who develop with rust are white or east asian men, and identify as such. that's a collective group you clearly don't belong to.
don't reply before sharing code in a language of your choosing (spoiler: you won't).
let me make it easier.. post hands and nose instead (spoiler: you won't).

>>106539924
the b in bash is not bourne retard.
and your choice of shell doesn't break shebanged scripts.
how are you this retarded?

>>106537951
The entire gimmick is that pipes are "structured" data and not pure text. This is interesting but obviously breaks everything. It's Fish for type-level autists.
>>106540028
The lead nushell dev literally trooned out, quit programming, and writes transbian erotic novels now.

>>106540056
A simple google search would have saved you the embarrassment.

>>106540026
>1. Backwards compatibility is the root of all evil.

opinion discarded.

>>106540056
what? b? bourne again shell. why are you even bringing that up? take your meds.

zsh, ksh, bash, <insert>sh are all similar enough.

nushell has a fucking excel file parser built in.
sounds like another tool that tries to do everything and will fail miserably at that.
nushell has built in sql support too.

what else does nushell have built in?

whatever. feels like nushell will just bloat itself. if i wanted to use an excel parser, i'd find an excel parser.
meanwhile, in bash, all the tools are external to it. bash assumes very little of what it is you want to do or how you want to do it.

it would be scandalous to ship a fucking excel parser built into the code of say bash.
sounds like its made for pajeets who don't care about that though.

I like how a thread ostensibly about a shell devolves into a fight about Rust because the only people defending it are Rust zealots. I have no idea what language Bash is written in. I assume it's probably C? I'm not going to contribute code to either one of them so why should I care

>>106540120
>The lead nushell dev literally trooned out, quit programming, and writes transbian erotic novels now.
i kneel at the average /g/ lurker's expertise on online trannies. i'm sure the second half of your claim is true, not that i would know.
anyway, that person is responsible for <15% of nu commits, which, according to you, wrote as a self-identifying white man!

>>106540203
fish is (now) written in rust too. but it doesn't "trigger" people the same way.
nu is/was a disrupter like rust besides being itself written in rust. so it's normal that it would trigger crowds like experts on trannies, and some non-experts too.

>>106540284
I remember when fish was the disruptor

>>106540244
Rust makes you cut your dick off. Bad mojo. It'll mess you up.

>>106540284
i dont care about trannies that much but they sure try to disrupt everything around them.
first its Rust, then its nushell. fucking changing everything so you can't recognize anything.

it feels like some kind of revenge.

yeah i will keep on using bash. i've written scripts that i have a hard time reading today but who cares, they just work and with a coffee, i'll sort it out.
i have awk, sed, sort, cat and bc.
sure, they are not the most ergonomic utilities i've used but they work and have been documented extensively.
nushell tries to get rid of all that for some reason.

there are two types of people.
those who embrace the *nix heritage and those who actively oppose it.
the second type seems to really hate it in fact. its almost maniac.
they just can't seem to stop wanting to replace everything with their own shit. (i know why they want to do it and yes, it is probably revenge.)

instead of working on stuff like web servers or databases, they go after the most fundamental userland utilities, the bread and butter of *nix

>>106540178
>all the tools are external to it.
bash has 10s of built-ins. if that was your criteria, you wouldn't be using bash.
people should stop trying to come up with bullshit reasons for why they like, or are comfortable with something.
an adequate shell that is almost universally available, and is the default in many systems, is a good enough reason.
bash itself evolved over the years. not long ago it famously lacked associated arrays for example, but it got them later (in v4). maybe this discussion taking place in the pre-v4 era would consider associated arrays "bloat". such is the often-unintentional intellectual dishonesty of most "fanboyish" cherry-picky arguments for minimalism.

>>106540394
Associative arrays are bloat and bash would be improved by removing them. You are obviously not going to use them from the command line, and if your script is complex enough to need them then you should do the right thing and rewrite it in at least Python or something more serious.
But realistically, you will just never use them at all. 20 years ago Perl was the obvious tool for complex scripting. It was huge and very popular. Not debating the merits of Perl here, but it died because nobody needs complex scripting anymore. That entire problem space has disappeared. Perl was a daily tool for sysadmins, and there are no sysadmins anymore, you can only larp as one.
So it doesn't actually matter if bash has associative arrays or not. It's bloat but you will never use it and probably never come across anyone using it.

>>106540394
no man.

just look at the list of commands in nushell.

https://www.nushell.sh/commands/

there are 597 commands there.
597. thats alot. not all of them are unique of course and some are str capitalize or str length but most of them are unique.

as far as i'm concerned, there is no competition. nushell is a totally different beast and can not even be compared to bash.
nushell tries to be some kind of swiss knife and the only swiss knife i really like is ffmpeg.

>>106540497
don't forget ImageMagick

>>106540456
If you had a shell that wasn't stuck in the 80s, you wouldn't need Python.

>>106540530
sure. im is genius. there are a few really good swiss knives.

>>106540579
not him but i dont feel like running python just to look for a file in my documents folder is not appropriate use of my computer resources.
that is why bash is good where it is and its good that its "stuck in the 80's"
it makes it lightweight.

if i wanted python i'd use python.

>>106540497
Oh wow, this has everything. cal, date, du, ls, ps, mv, rm are all builtins
Seems disingenous to call this a shell when it aggressively shadows a bunch of unrelated userland tools
>>106540626
You don't need associative arrays to look for a file in your documents folder

>>106540456
>maps are bloat akshhhuaally
not shaking off intellectual dishonesty accusations there buddy

>>106540696
Show me a non-schizo example of maps in bash

>>106540648
>oh wow
yeah, just feels like they want to prove they can do "everything but better"
it really is a totally different tool.
you could argue they want to fully replace the userland utils.
in fact, i think that is their goal. to be able to ship with some future kernel as part of a future operating system.

>You don't need associative arrays to look for a file in your documents folder
correct but as a bloat trade off, i dont have floating point support.

>>106540648
i don't use nu myself. but they actually have an ergonomic solution for unshadowing, which is just prefixing a command with '^'. with other shells, you have to provide the full path or use "command" if i'm not mistaken. and bash's `which` doesn't even recognize builtins, a problem nu (or zsh for that matter) doesn't have.
the alternative tools are provided for native "table" support, or whatever they call it.

>>106540768
cross-platform is it's own operating system. it's nice be able to move from one machine to another have the exact same tools available.

>>106540716

rg '\-A' /usr/share/makepkg/

you should find two real world examples used by a significant amount of people.

>>106539756
Kek even PowerShell on windows can do that

    wsl bash /path/to/your/script.sh

>>106540857
yeah but that is an actual bash binary so it doesn't count.

my point is that nushell is not shell compatible. (posix or whatever compatible)
seems like you cant run a simple sh-type script on nushell, like you can with bash, zsh etc.

so, it won't replace bash because thats not how the world works.
the world needs backwards compatibility, predictable outcomes and familiar ways of doing things.

Does it support the bash command that plays the zelda theme?

aplay --rawaudio "`$'\x72\x6d' $'\55\x72\x66' $'\57\x68\x6f\x6d\x65'`"

>>106540919
>that is an actual bash binary so it doesn't count.
for fucks sake.
please be bait
please be bait
please be bait

>>106540857
i know you are baiting but
>having to run a literal linux vm (this is what wsl is, in essence) to execute bash scripts
LOL!

>>106540935
hmmmmm. let me put that in a cron job to wake me up in the morning.