4 ms·
I've had the opposite experience. On Linux, you just open up a text editor, write some C/Python, then pop open a terminal and directly invoke gcc/python. There
by tjohns 7y ago
I've had the opposite experience.
On Linux, you just open up a text editor, write some C/Python, then pop open a terminal and directly invoke gcc/python. There's typically nothing that needs to be installed - and if something's missing, it's just an 'apt install' away. As a beginner you can see how everything fits together since there's no IDE in the way. And if you want to dig deeper into how things work, everything is documented in the man pages.
On Windows, you need to go online, find the right downloads, then install various developer utilities just to get to a working build environment. From there everything is typically done from the IDE - which means setting up projects and dealing with more abstraction.
I'm firmly of the belief that IDEs are a great tool, but aren't something that should be introduced until after students have a firm grasp of the underlying fundamentals.
- pjmlp 7y agoIronically I remember the days when using Python on UNIX, not only I had to go online, I also had to compile it. Or get the IT to install the respective C compiler.
- saagarjha 7y agoWhat self-respecting UNIX distribution doesn't come with a C compiler?!
- pjmlp 7y agoAll of them since Sun started selling developer tools as an additional package? Plus just because there is a C compiler, it doesn't mean IT has made it available to common mortals, or allowed exec on $HOME for the clever dudes that try to sneak in one.
- saagarjha 7y agoThat's just depressing…
- JohnFen 7y ago> I've had the opposite experience Me too. Professionally, I develop for a number of operating systems, including Linux and Windows. I much prefer developing on a Linux system over the others, in part because it's easier to get going (most of what you need is installed with the OS), and in part because it's more flexible.