I mean, diskpart and dir don’t make especially any more sense than lsblk/parted and ls. A fair point can be made for ‘copy’ being more intuitive, but ‘diskpart’ means you had to learn what disks and partitioning were, and lsblk means you need to learn what ‘block’ devices rae, and of course ‘parted’ references partitions. ‘dir’ means you wanted to ‘show the directory’ which means you had to learn of it as a directory, but then learn that the shortname of directory is the way to see the contents of a directory. ls means you learned you want to ‘list’ contents and that unix had this laziness of just the first and third letters of a word. Both involve learning, neither is ‘intuitive’.

You end up writing ridiculously long commands

I assume this is the likes of dbus-send and crap, and I agree with you if that’s the case. Dbus is a complication I could do without and have to confess that powershell cmdlets generally do a better job of instrumenting the system than a system that increasingly has no specific help and only long dbus-send commands to tackle certain things. dconf has issues too, but I think does a better job than the Windows registry at analagous function.

Its called learning. I know both sets of commands because I have chosen to.

Though I personally have the feeling in exactly the opposite way, having used unix-likes for most of my adult life, I won’t argue with you on the principle of the idea (for obtuse syntax e.g. dd the disk destroyer or the infamous tar command come to mind).

At the same time… I really don’t think you chose your examples super well here.

cp and it’s mv companion don’t seem more ‘obtuse’ than copy written out in your example.

ls following the same two-letter logic for ‘list’ also does not seem out-of-this-world crazy syntax. In fact, I always wondered more about dir to list things, especially in a world where the things it lists are technically called folders not directories.

This same logic once again extends to lsblk to ‘list’ what? ‘block devices’ which describes all sorts of storage media in unix-land. Sure, it’s different, but in these specific examples I definitely don’t see an objective better/worse option. I mean, similar examples for obtuseness could be made e.g. for why the primary drive starts with a C: on windows, or why we have magical drive letters at the beginning at all if you come from the opposite paradigm.

And lastly your disk example is equally written as fdisk --list which once again just describes its own operation.

Dunno, I think both systems have their idiosyncrasies which you just find weird if you’re used to the other.

I’m the same, but with windows.

People just don’t like changing their ways.

Also you’ll find out that linux is mostly much more logical than windows ever was.

This is why I appreciate immutable distros so much. Sure, you can’t really do super sick stuff by tinkering with system files or modify some system components to make it your dream system, but the average user really doesn’t need that. In most use cases, the flatpak version of a software will just run fine, sometimes even better than the standalone version due to certain outdated dependencies being hard to acquire/install that the Flatpak just integrates. Sure, Flatpak also has issues, but for the most part it works for the end user.

Not if I’ve never bought a prebuilt PC.

Yep, and not a small price at that. While the home license is not as expensive, it’s still mid two digits. IIRC pro version typically costs around 100 € even as the bundled OEM license, especially if you’re buying a laptop from a smaller manufacturer. That’s the amount I remember the price going down if you drop windows licensing from a corporate laptop lease.

In any way it’s not an insignificant price.

You’re forgetting piracy. I didn’t buy any parts with OEM licenses. Granted I went grey market for my Windows 10 so I paid someone like $20.

Aye, I did buy a prebuilt once in 2004.

At least nowadays it’s so much easier to find FreeDOS laptops. I remember that it was not a thing here 20 years ago, and Windows was included in the warranty so you couldn’t remove it for at least 2 years (if you care about warranty).

Nah, not for me. I have only built my own PC’s since 2006. If i had a laptop (and a few surfaces) it was through work.

I know all about the OEM license thats now hardcoded on the board due to my job. Our company was buying devices with windows, essentially paying more per device, then imaging them with our image with an enterprise license…

Yes, but no. They know you’ll pay (e.g.) $700 for a PC. If windows were free, you’d still be paying $700. It would just go to a different billionaire.

Hey now, most of us didn’t imagine that we were funding Bill Gates to go get an STI from Russian children. That adds a layer.

Eh, whatever floats your boat, I say, no kink shaming

Same… Multiple times.

now it does too since I dont really do much gaming anymore.

Tbh now gaming just works on Linux. I primarily game and I see no reason to ever go back.

Quite the one-way argument you have there.

While Windows broke the printer driver, Linux didn’t have a driver to begin with.

And Windows forces updates because otherwise you have people who would never update and then complain that their computer gets hacked.

Switch those users to Linux, and they would complain a lot more while breaking their entire computer, including hardware.

I became more aware of things breaking on Windows after switching at home. Everyday there is some weird bug or just very inconvinient behavior coming from Win, Office or platform-exclusive software. And with everything screwed to the floor and witholding information, you either find a sketchy workaround or wrap yourself around the issue. It’s so weird, like I took a red pill. Linux quirks are challenges that I’ve chosen for myself, and there were several huge problems, but oh well going into windows is not a safe haven either, and that’s a paid product and a standard OS for PCs.

I don’t think I have anyone in my family that I hate quite that much.