majkinetor

It auto updates, and this issue is forever.

That is exactly what happens to me

We should but we probably wont. There is such thing in my country named something like "piercing the corporate veil", when the deeds are dimed so bad that state goes after owners, but it was never used in practice.

I use it on Low or Medium as recommended. It just went nuts.

Because you are making it better for us, non MS people (its also already fully open source). I cant understand this way of thinking. Companies are not good or evil, they are abstract entities with people behind them and tones of regular users around. Besides, no fatureset will ever fit everybody, customization is a thing.

Its good to hate bash specifically. The language is so terrible, low on standards, bad discovery. The only good thing about bash is it is pre installed. Its not far away from batch (.bat).

And you are wrong, who says that is the correct way. The correct way is the one that works

    tnc dns.google -t

I didn't even have to look for the alias, there is standard naming for them.

Like I said before, people who complain just didn't RTFM and got out of their comfort zone.

sal ls gci >> $PROFILE

its faster then this discussion.

Such a drama without a reason.

Its not slop for one. Take a look at repo and its practices. Its mind blowing and predates AI.

Nushell is nice, but lets not get carried away - it is decade away from pwsh, and suffers from the same things you complained, with language and semantics that are not intutive as pwsh's and not nearly as complete. Besides, so many 3rd party supports pwsh like Sql Server, VMware etc.

I agree that MS should push it way more and make Linux variant even better. The problem is that pwsh hardly surived at MS (cudos to Snover for being stuborn and worked against his position at MS to make it happen), and that needs some opinionated people working in MS who can fight this battle (I could honestly dedicate my life to this, I offer my services, for both pwsh and Windows, Microsoft!).

No. I use aliases so its as quick as with bash, but I am faster as I don't have to lookup for params due to fantastic discovery and usability features.

With longer commands, auto complete is also viable. I hate some long forms, like % vs ForEach-Object and ? vs Where-Object, its just ludicrious that someone would insisit in using full forms of those.

Things like `ps | ? name -like w*` or `1..10 | % { irm https://.../$_ }` can't really get shorter and I use them all the time

Auto complete on params is epic. Type -e and ctrl space to see all params starting with e along with their aliases. Verbosity is good thing in that case, as -ea doesn't mean much when you are new to this.

    ps -e<CTRL+SPACE>
    ErrorAction    ea             ErrorVariable  ev

The verbose practice is not meant for interactive use, but for sharing scripts.

That is just common invalid trope. You can make scripts look shorter and more "culturally fit" than bash. Its just that people prefer more verbose variants for some rasons (I don't). There are automatic converters too. The legit reason is to make script cross platform, as that is easier with verbose form.

That is my only complaint really. Lets make it there... I beleive main offender is .net, but also main feature enabler.