Now I know that C can be used for do web programming.
With regards to #26,If I am using notepad++,good thing is there is color coding and (new tab)->can open up another space.It also run faster.Cons is it doesn't tell me what error I made,I need to go to Console->Right Click and copy down the error message and search how to resolve.
For IDE I can use F5(Build Project) , F7(Run Project) and save the solution,
it also tell me what mistake I made in advance.
TS, I can see that you're reliant on the Intellisense (auto-completion) feature and Auto-Correct feature in Visual Studio. Nothing wrong with it. Since modern IDEs are all providing this feature like it's a basic thing.
Just to share why davidktw may sound harsh at time. davidktw and I are trained from the old-school era (maybe 80's, 90's), when an IDE was just a
plain text editor like Windows Notepad with fixed width font (perhaps DOS white text on blue background with no syntax coloring even). They had no Intellisense auto-completion or auto-correction feature -- considered advanced and alien technologies for our time -- and we probably started programming, compiling and building from the command line manually from scratch. No
F5 to Run or
Ctrl-Shift-B to Build. We also had to read and interpret the error and warning messages line-by-line from the compiler to understand the problems and fix any problems manually by hand. There was no smart IDE from Microsoft, Borland or Watcom that suggests remedies or solutions for auto-correction. Through this process, we had to learn (and do) things the hard way and to learn how the preprocessor, compiler and linker behaves out of necessity.
There was also no Internet, WWW or Google in the 80's or 90's. We had to consult hardcopy printed documents for programming API. They were like the "Bible" (authoritative reference) of sort for programmers. When I was learning C/C++ programming, the API was printed as an Appendix in my Pearson's textbook. After consulting it far too many times, we became familiar with an API and committed those functions and classes to human memory.
I can perfectly understand if you're trying to rush out a working program for an assignment or work, or just want something that works. You may not be interested or too rushed to understand why a compilation or build fails or how a compiler behaves. But it's up to you how far and how deep you want to learn. Not everyone is motivated in programming, as much as everyone has their own personality, inclinations and hobbies.
I consider myself a senior citizen in the IT industry already since it moves so much faster than all other industries combined. Knowledge of an IT product or platform is easily superseded within 5 to 10 years max.
I notice newer generations of IT students in the last decade have no problem banging out programs in high level PHP, Ruby, Java, .NET, JavaScript and Python. But they are quite adverse or unused to lower level old school stuffs like C/C++/Perl. Maybe can leave them to old folks like me to maintain. But I've not reached x86 assembly language yet. Coding in assembly and raw machine code is epic to the max.
