881
The fact that you canβt run through Windows setup w/o internet and an online account is absolute bullshit
(lemmy.world)
this post was submitted on 24 Aug 2026
881 points (97.8% liked)
linuxmemes
32600 readers
1588 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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 of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
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
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
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 figures
We 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Which one is that? Powershell is way more intuitive than bash and I like bash.
bash is more intuive than pwsh imo.
See my other response on this thread for my reasoning. If you still disagree I'd love some guidance on how to use bash more intuitively.
Is it? I find them both equally unintuitive tbh. You really just have to memorize the commands you frequently use, or keep looking them up.
Powershells commands are "Verb-Noun" and it makes it easy to search for the command you need. For example Get-Help Get-* will give you a list of all the "Get" commands and a brief description of what they do. Get-Verb will list the approved verbs so you know what verbs to search for. All within the shell. If there's anything like that in bash I haven't found it. I always have to search the web to figure out what I'm trying to do with it. Which can be annoying if I'm working directly on a headless system. Powershell also has aliases built in for bash and cmd commands so you can use those if you're familiar with them. I hate Microsoft but it's one thing I have to give hand to them.
That's not to say bash is bad. It's great. It's just not nearly as intuitive.
In bash if you type the verb, then hit tab it will list the possible options, right? Is that not the same kind of thing?
Tab completion isn't really what I'm talking about here. Powershell's intuitiveness comes from the ease of finding the command you need. For instance if you type "copy" into bash and hit tab you're not going to get anything. That's because the command for copying a file in bash is "cp". Now, how do you find that out using only the shell? You can use apropos, but who's going to be able to figure that out without a web search? I had to try several variations of "find commands in bash" just now to get Google to mention it. Most things in bash are like this, there's no real naming convention and most of the time the names are pretty meaningless by themselves. It's a big barrier for people who are new to it or only use it sporadically.
Conversely, typing "copy" into powershell and hitting tab you will get a number of options which shouldn't take much for a beginner to locate copy-item from there or you can find it via the previous methods I mentioned.
I genuinely think you may just be more familiar with PS. I use "Get-Printer" all the time, but it's not like I was able to discover that command or syntax without web searches. Same with "cp" in bash. I had to learn it and use it, but I'm never going to forget it now. Something that seems inconsistent/unintuitive to me in PS, is some commands specify an object with:
Other times it's like:
I keep a notebook handy for things that I use as frequently as several times a week.
Searching commands online is a perfectly valid way to find things, especially if you don't know how to discover them within the shell. My point is that powershell is fantastic for that and bash is not. Years ago, I read maybe 1/3 of a powershell book and it was enough to set me off and figure most things out on my own from there. It's rare I have to go online to find something. I've read/watched quite of bit of bash content over the years and I can't say the same. I still struggle with it or have to go back and check my notes all the time. I am more familiar with powershell but I've been using bash quite a bit longer. For me that highlights what I'm talking about here in terms of intuitiveness.
As for the inconsistency issue, I'm sure there are inconsistencies in either shell but I'd need more information to explain this one, the only time I can recall something like what you're referring to would be commands where -Name is a parameter, vs something like a -Filter parameter where you entering name as what you're filtering for but that would need more than -Filter Name "name" to work(I think). For the most part I find powershell to be very consistent once you understand what's going on. Bash as well, but it's harder to get to the "understand what's going on" stage.
Powershell is just json with jq abilities
But it is intuitive. There's no arguing that.