this post was submitted on 27 Mar 2025
999 points (90.7% liked)

linuxmemes

24192 readers
1538 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 87 points 5 days ago (4 children)

    The commands: ls cp mv...

    Meanwhile you get Windows people who memorize things like Get-AllUsersHereNowExtraLongJohn

    [–] [email protected] 34 points 5 days ago* (last edited 5 days ago)

    Get-ListOfFunnyPowershellReferences++

    (Seriously...ExtraLongJohn is damn funny)

    [–] [email protected] 14 points 5 days ago (1 children)

    Get-command -noun <string[]>

    Handy AF

    [–] [email protected] 21 points 5 days ago (4 children)

    Versus:

    man $commamd

    PowerShell might be okay script syntax for people with uncorrected sight issues and the elderly who's heart might not handle bash without set -e but to be useful as a CLI shell prompt that is your primary way of interacting with the computer like it can be on Linux it needs to be so so so much shorter. I'll be dead by the time I type out half the shit it'd be like 4 key presses total on Linux.

    And that's before you get to the issues of it being a whole object oriented and typed programming language with .NET whereas shell is nice universal text everywhere that can be piped around however you want.

    There are even those absolute mad lads who unironically use PowerShell on Linux.

    Learning the absolute basics of how to use tmux, vim, sed, awk and grep and pipes and redirects and the basics of handling stdin and stdout genuinely made me feel like all my life I was an NPC in the matrix and now I'm Neo just because passing around bits of text is so powerful when everything works on that basis.

    [–] [email protected] 15 points 5 days ago

    Yea, when I switched to Linux, at first I installed PowerShell to get something familiar, but quickly realized that contrary to Windows, terminal on Linux is actually usable on it's own out of the box.

    [–] [email protected] 3 points 5 days ago

    Re: length of commands, PS commands are longer, but they also have tab completion so realistically you never type the whole thing, only enough to be unambiguous and press tab. I'll grant it's still longer than the equivalent bash, but not by as much as it appears.

    [–] [email protected] 4 points 5 days ago (1 children)

    PowerShell doesn't stop on errors either by default. And of course a significant number of tools you need aren't available in PowerShell, only cover partial functionality or are an exe you need to call so even if it did stop on error, doesn't work for those tools by default.

    [–] [email protected] 5 points 5 days ago

    It is still a shock to me that some genius aliased curl to Invoke-WebRequest and that curl.exe is what you actually want.

    [–] [email protected] 2 points 5 days ago (1 children)

    I'm one of those that use PowerShell on linux.

    You can use tmux, vim, sed, awk or whatever binary you want from PowerShell. Those are binaries, not shell commands.

    You can use pipes, redirects, stdin and stdout in PowerShell too.

    I personally don't regularly use any object oriented features. But whenever I search how to do something that I don't know what to do, a clear object-oriented result is much easier to understand than a random string of characters for awk and sed.

    [–] [email protected] 3 points 5 days ago* (last edited 5 days ago)

    Mixing the two philosophies of coreutils and unix bins and whatever is happening in PowerShell seems even more unholy to me than the phrase "object oriented result", but different strokes.

    I gave up on PowerShell on Windows as a plausible alternative to Bash on Linux the minute I realized there's no real equivalent tocat, there's type or if you hate yourself - Get-Content which is aliased as cat but doesn't really work the same way.

    If I can't even very basically list a file irregardless of what's in it, it's just dead out of the gate.

    On Linux, I once sent myself an MP3 from my server to my laptop with cat song.mp3 | base64 -w0 > /dev/tcp/10.10.10.2/9999 because I cba to send ssh keys.

    I'll give modern windows a few points - the new terminal emulator application is sweet, and having ssh makes it easy to login to remotely.

    PowerShell is a strange programming language that makes me wish I was just writing C#.

    Bash is a shell language. At its heart it's a CLI, emphasis on the I, it's the primary way of interacting with a computer, not a way to write programs. Even awk is arguably better suited.

    That's why it neither needs to be verbose nor readable for complete beginners, you memorize it the same way you memorize where buttons are on a keyboard or what items you can expect in a right click context menu on Windows.

    Most bash scripts people write are far too complex for it and could stand a rewrite in perl or python or heck, what I think actually works amazing as a "scripting language" - C.

    [–] [email protected] 2 points 5 days ago* (last edited 5 days ago)

    In PowerShell most common cmdlets for basic operations have aliases by default. And funnily enough you can use both Windows (cmd.exe) and Unix shell names for these. (copy vs cp, del vs rm, etc.)

    AFAIK The cmdlets that you use only by Verb-Noun convention are mostly used in scripts, or in some administration tasks.

    I also think that some poeple miss the point of PowerShell, as it's not supposed to be worked with like with Unix shells, since it's more object-oriented than string-oriented.

    [–] [email protected] 1 points 5 days ago

    Long long maaaaan