From my experience, there's a lot of console stuff that isn't actually harder on Windows per se, it's just that there's a lot more help out there which is directly related to Linux than Windows (and that help also tends to apply to Unixes like MacOS).
LaTeX is a good example actually: I absolutely have LaTeX working on Windows and it really is no harder than when I've used it on Linux. But if you google anything, you always get references to things like ~/texmf/tex. I know on my system that I need to actually go to C:\texlive\texmf-local\tex, but working out how to translate all that stuff takes some time and experience.
Another example would be adding a folder to the TEXINPUTS environment variable. Taking the first stack exchange answer to the first result on googling 'latex TEXINPUTS' says to do export TEXINPUTS=.:/path/to/the/local/folder//:. But to do that on Windows, you need to know how to edit Windows environment variables: Control Panel -> System -> Advanced System Properties -> Advanced -> Environment Variables... - that's two levels deep of clicking something that says 'Advanced' - and you need to know how the GUI it pops up works - there's two types of environment variable, which might be confusing if you don't know why - aaand you need to know that the colons in the Linux command above is the path separator, which you need to replace with semicolons on Windows.
That's a lot! It's the same level of required minutia that Linux generally gets historically criticised for, except that there's now a lot more stack exchange answers and random blog posts to help the Linux user than the Windows user. But it's certainly not an insurmountable amount of knowledge, and there's plenty of times on Linux where you end up in similar holes where there just doesn't happen to be the same blog post coverage on what to do.
Log in to comment