3 ms·
Having been taught programming at university with command line tools (Ocaml, then C with GGC on Linux) I've naturally gone the same way when self-learning C# on
by titanix2 10y ago
Having been taught programming at university with command line tools (Ocaml, then C with GGC on Linux) I've naturally gone the same way when self-learning C# on Windows: notepad + Powershell + csc.exe I found somewhere within .net framework installation folders. I sticked with it for simple programs and started using Visual Studio 2008 only when learning GUI programming.
So I always find strange all the C# tutorials and books starting straight out with Visual Studio: this software is often updated with major visual changes thus rendering screenshots obsolete and there is a lot of visual complexity involved especially for beginners in both C# and programming. On the other hand the CLI interface is pretty stable, simple to use for small programs with few references -- and it's actually force one to understand what a referenced dll is -- and involve less magic.
- amorphid 10y agoWhen I did a bit of programming in Java, I was using Intellij. I found that starting with the IDE made learning the fundamentals harder. I later switched to Sublime and a command prompt, and found the process of pushing through command line errors to be more instructive.
- jamra 10y agoMerging csproj files in source control is also a pain. I think they tried to get rid of sln and csproj files but got vetoed by the community.
- douche 10y agoI did the same thing with Java, for the longest time. Makefiles invoking javac, almost the same as I did for my C/C++ programs. It does start to break down once you start to get into more heavy-weight programs. I wouldn't even want to see what a hand-made makefile for one of my C# solutions that has a couple dozen projects and a few hundred code files would look like...