All while technically selling alpha versions...

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.

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 understand your issue with the terminal. I think that it could be fixed with Oh-my-zsh for a personal computer. I have mine setup so I don't have to remember the entire command, just the first letter and it shows me all matches. I was proficient with both batch and powershell, but bash scripting is even easier.

Yeah, I had given up Linux for over a decade, but Windows 11 has brought it back out... And tbh I like it better as an adult. Now I run Windows in a docker container only.