The last thing I want to do when learning a new programming language is waste a lot of time trying to install all of the dependencies/libs/compilers, being nagged by the OS to reboot because updates were installed, having cortana randomly pop up (it's like the modern day clippy), and deal with a host of other things that windows does to get in your way.
The important part of learning to program is sitting down to program and sticking with it despite its difficulty. Developing habits of mind is what makes a person a programmer. A lot of beginning programming resources are OS agnostic because they run on the web and Firefox/Chrome/Edge/Safari/etc. are fungible (and of course HTML/CSS/Javascript are also OS agnostic).
Going with "the operating system you are using" does optimise quite a few things; these are the "pros" of this approach, things like:
- not burdening yourself with the learning curve of a new OS at the same time as you undergo the learning curve of programming
- being able to ease the programming effort by taking advantage of microefficiencies you've already gained from friend use of the OS.
- etc.
This has to be weighed against potential cons though:
- how long do you intend to program for (presumably some large multiple of the time it would take to learn a new OS)
- what is the actual difference in overhead of using development tools on the two OSes–if you're repeatedly undergoing a little extra overhead for every dev task on your current OS, this builds up over time
- if you intend to simply defer learning Linux to a later date, what's involved in switching your dev setup over? Will there be habits and disinformation to unlearn in the process?
The only certain thing Linux is the best operating system for is learning Linux. Learning Linux is not learning to code. It is not a step on the path to learning to code. Mostly, it is a distraction from getting started. There is time to learn Linux later...http://norvig.com/21-days.html
Good luck.