12 ms·
C is great. I wouldn't recommend starting programming in C, though. At least not with the standard exercises you see. Get user input, read a file, do this do th
by bluedino 11y ago
C is great. I wouldn't recommend starting programming in C, though. At least not with the standard exercises you see. Get user input, read a file, do this do that with it.
Why? the C standard library is full of gotchas and tricks and goofy shit that makes it unsuitable for new programmers. The comp.lang.c FAQ should be standard reading material for anyone taking a C class. Look at all the posts on StackOverflow about the stdio functions 'not working right' and asking how to do menial things like collect keypresses.
C works well as a first language if you teach it like assembly (use of which as a teaching language is another debate): flip some bits and do some loops. But not for collecting user input/output. Half of your students are going to get stuck trying to collect a list of names from the user, before they even get a chance to get stuck trying to sort the list.
- tosseraccount 11y agoOvercoming goofy shit and gotchas is part of any programming system.
- mrestko 11y agoYeah, but why start with an exceedingly painful one except to needlessly inflict pain and suffering on students. Better to lay the groundwork with a friendlier language, learn the basics, and then move on to the more complicated gottchas (at least in my amateur opinion).
- bxh 11y agoWhat language would you suggest is friendlier, and less rife with gotchas? I find the rules of C fairly reasonable, at least on the surface.
- pklausler 11y ago#include <stdio.h> int main(void) { (printf)("C is awesome\n"); return 0; }
- pklausler 11y ago#include <stdio.h> int main(void) { (* * * * * * * * * * * * * * * * * * * * printf)("C is awesome\n"); return 0; }
- bigtunacan 11y agoIn no particular order any of the following as an introductory language. Ruby -- puts "Hello World" Python -- print "Hello World" Lua -- print("Hello World") Personally I wish every programmer would eventually learn C. Getting down to that low level and really understanding how things work is important, but if it is the first language I think we would end up with a whole lot less programmers as many would give up early.
- tosseraccount 11y agoRuby is written in C Python is written in C Lua is written in C
- bigtunacan 11y agoI'm not sure how that is pertinent. Programming languages as a general rule are initially implemented in some other programming language and then potentially later bootstrapped with their own language. Ruby has also been implemented in Java (JRuby), Ruby (Rubinius), .NET (IronRuby), JavaScript (Opal). Python in Java (Jython) and .NET (IronPython) Lua has been implemented in too many language for me to list them all here (C, C++, Lua, JavaScript, Erlang, OCaml, Go, etc...) It seems C itself was initially bootstrapped from B which was bootstrapped from BCPL. If we were to follow this to it's logical conclusion I'm guessing we end up at some version of Assembly. Are you suggesting we should start budding programmers on Assembly?
- tosseraccount 11y agoNo. Just stick with C so that it's portable and fast.
- antod 11y agoI don't write Python in C /s You meant Ruby, Python and Lua have their reference implementations written in C. They all also have other implementations written in other languages.
- 11y ago
- ArkyBeagle 11y agoThe drop from Pascal to 'C' is pretty short.
- Apocryphon 11y agoJavaScript has been touted as an intro language, and in some ways it's even quirkier than C.
- livarot 11y agoRecommending JS as intro language is just plainly wrong.
- DyslexicAtheist 11y agoMy first language was C and I loved it. Maybe it takes a certain type of mindset and tenaciousness (madness?) that will put up with the gotchas. It was exactly those gotchas that got me hooked though. It was similar gotchas that made me love Linux the terminal, vi etc ... The argument that one "should study other languages before they're fit to learn C" is terrible IMO and somewhat condescending. It's like saying one must learn "nedit/pico" before starting with editors like "emacs/vi". Please stop repeating that - especially if you have not done much C. I am probably too old to understand the constant hate and criticism on why C shouldn't be taught to beginners. Not everything "has to be easy". Starting with C & Linux, I always had an advantage later in my career because it was these skills that enabled me to drill deeper than those who didn't know C & system programming. C isn't just hard for beginners because of the language but the rest of the tool-chain. If you can get over this then learning C will also teach how to debug with gdb, strace, valgrind and learning about low level system calls, and a great deal about how a program can be loaded/structured e.g.: dynamic & static linking. Also where the resources are used and how to eliminate it’s bottlenecks. What is a heap, stack or static memory? How does memory management or garbage-collection work on a modern OS? What is IPC and how do the individual system calls function & require as input? How do you compile a program and optimize it for different target platforms? How do you write Makefiles or use autotools etc ... Tell me again which other language forces you to learn these things? You could easily build a career just on C & Linux because of this "additional learning curve" and extra knowledge that a good C developer will have. Sorry for all my bias (as I said my views might be very outdated :-))
- dllthomas 11y ago> The argument that one "should study other languages before they're fit to learn C" is terrible IMO and somewhat condescending. I think I agree. > It's like saying one must learn "nedit/pico" before starting with editors like "emacs/vi". It's very little like that. Other languages have their own strengths in a way that nedit/pico do not.
- marcelluspye 11y agoIt sounds to me like you haven't spent much time trying to teach a class to program. Most introductory courses these days focus on trying to teach students to understand how to solve problems (usually to some degree agnostic of language) and then how to turn their solution into code. The largest mental leap seems to be with the former, and using C as a starting language makes the latter unnecessarily difficult compared to, say, python (which is why it's gaining such popularity among intro. courses I can understand if one is a) very motivated and b) has the right mindset to properly frame their ideas at the low level c operates at, C could be a good starting language. But this is not the case for many beginners.
- arc0re 11y agoI started with C and it took me 3 good years fooling around with other languages too to get a "good" understanding of C. Better learn with higher level languages indeed...
- agumonkey 11y agoWhich languages ? How common is it for people to get better understanding by travelling in other programming cultures ? My personal experience goes this way but I rarely hear it.
- ufo 11y agoI'm not the parent poster but in my opinion, any language that doesn't frustrate the beginner is fine. The most important thing for learning is practice and if that is not fun people will end up quiting to do something else.
- agumonkey 11y agoI hesitated to say that, but to me the most important part is paradigm and structures/patterns. lisp will teach you untyped tree recursion and metalevel perspective. ml/haskell will teach you typed composition. prolog goal based space exploration. forth stacks. APL arrays. C/Pascal etc are supposed to teach you 'imperative' but I believe imperative is mostly a conflation of lots of things, mutable state.. at best you'll learn state machines.
- sklogic 11y ago"Unsuitable" is far too strong a word. It was ok for generations to follow the K&R examples, and now it somehow suddenly became "unsuitable"? I'd say it's just "somewhat more tricky" and "got a slightly steeper learning curve", that's it.
- kungtotte 11y agoIf you start with C as your first language you're not really starting out by learning how to program, you're starting out by learning how the computer operates. I'm not saying this is necessarily a bad thing, mind you, but it's important to note the distinction. Using an analogy; starting out with C is like learning to drive by being told how an internal combustion engine works, and then you're asked to wire up your pedals manually and install a fuel tank of sufficient size before you're allowed to learn how to put the car in gear. Those are all useful things to know, but you can learn them after you know how to drive, and your knowledge of either topic (driving and automotive engineering) is not in any way impaired by learning it in a different order.
- sklogic 11y agoWhy? C is a very high level language. It is not that dramatically different from Pascal, which, in turn, is almost a pseudocode from your algorithm textbooks. You can learn fairly abstract concepts with C without caring at all about how it maps to the hardware.
- jdbernard 11y agoThis is a strawman. The author is not advocating this as a first language: "Learning C is not necessary for everyone, but there are many posts on Reddit and programming forums with authors who feel like they’re missing something, and I wonder if this is part of what they’re looking for."
- nikdaheratik 11y agoYeah, seems to be some confusion of the title. Probably a better title is "Why learn C programming?" The article itself isn't about "Learning to Program with C as a beginning language". And I don't know how I feel about C as a first language. I don't believe it would be worse than Java, which was the intro course at my Uni, but my first language was BASIC of all things, which is good in some respects as it really is a "Beginners" language, but both C and BASIC could encourage sloppy practices without good instruction and C especially has some gotchas.
- bitwize 11y agoI think that if you are going to teach someone the craft of programming (which is different from computer science) -- really teach them, you should follow what I call the Old School Curriculum. The Old School is based on the way many kids learned to program in the 80s, and the 80s version went: first BASIC, then assembly, then Pascal. The first language you should learn should be a doddle to learn, even if it isn't very powerful. This was BASIC (or sometimes Logo) back in the 80s, but you could probably substitute Python or even Scheme today. This language teaches you concepts like these: * Computers follow instructions supplied by the programmer * The instructions have to be carefully worded in order for a computer to follow them (i.e., intro to errors and debugging) * Arithmetic and mathematical operations a computer can perform * Computers can remember things (i.e., variables) * Computers can interact with the world (input and output) * Computers can make decisions (conditionals and program flow control) These are the very fundamentals of programming and it's amazing how many people haven't internalized these concepts at a deep level. You can actually get very far with BASIC -- entire companies have been run with BASIC code. (Software written in and for Business BASIC variants was a major industry back in the 1970s and 1980s.) You can get even farther with Python. But once the learner is ready to go deeper, it's time to begin Phase 2. The second language you learn should be assembly, which familiarizes the programmer with how a computer actually works at a fundamental level, as well as important concepts like CPU word length, memory addresses (essential for understanding pointers), program call and return (and stacks), etc. You don't have to even complete a large project written in assembly to get the benefits of this low-level, bit-twiddling learning. Finally, the last language you learn should be Pascal. C or C++ would be today's equivalent. In this phase you synthesize the knowledge of high-level programming, structure, and control flow that you learned during your "BASIC" phase with your low-level understanding of machine details that you learned during your assembly phase. Then, the details of how and why the language works the way it does make much more sense. So yes, to me it makes total sense to teach C -- as (at least) a third programming language, perhaps after several years of proficiency are acquired in the other two (depending on the student).
- im_a_bug 11y agoHarvard's CS50 begins with C and it's quite successful. Well, technically they begin with Scratch, but the course quickly moves into C. They get around certain barriers (you mention user input) by providing helpers/abstractions, which are gradually torn down as the course progresses.