Hacker News Reader

Comment by sokoloff | Hacker News Reader

I suspect there are CS programs that don’t even teach C at this point.

That seems really weird to me. We even did a machine language course even though we will never do any machine language programming. It's good to understand what the hell is going on. C is amazing in explaining how memory management works, since you have to do it all yourself.

C teaches you how PDP11 memory management works. Modern PC/server hardware doesn't work like this, neither do modern applications that use accelerators, and while the system works hard to present this virtual address space to your runtime, you don't need to think about it in many languages, from LISP to Swift. Most devs write Javascript.

I say this as a person who loves C and taught it lovingly to undergrads for many years.

Embedded system programming is a lovely niche, but we don't need to design CS curricula around it.

I would hope you wouldn't be designing cs curricula around javascript, because even javascript frameworks are moving to typescript.

This seems like not teaching calculus because you can do it on a calculator. I didn't do a degree that focused on C development, but I still had to know how to do it. God forbid any of your graduates end up working on an operating system at some point.

> I would hope you wouldn't be designing cs curricula around javascript

I didn't propose that.

I'd expect a good curriculum to expose students to several languages, so that picking up another one is not an ordeal.

Someone beat me to the punch, but yeah, at this point, C barely works the way actual computers work under the hood. It works the way a PDP-11 does, and most modern computers have been forced (even at the CPU level) to basically act as PDP-11 emulators.

Take, for example, the entire stack-and-heap thing. That's not a bedrock feature of computing; it's merely a thing that was particularly convenient to do on a PDP-11. But if you're working in C, you have to do it - so it stays a "seemingly bedrock" feature even if the hardware has drifted far from the PDP-11. A lot of these features boiled down to the ISA making it fairly convenient to do them that way - there were built-in instructions that made it pretty easy to "color-by-numbers" and get the job done.

---

This is similar to how we (societally) did barely any woodworking with screws before we had the industrial processes (like lathes or whatnot) to make them. Nails weren't some magic ground-truth or axiom of woodcrafting - it was just obscenely difficult to craft a screw, so why would anyone in their right mind attempt to build something with them?

Screws are a terrible way to build something still though compared to a properly fitted mortise & tenon.

For an undergrad course on compilers that I took, I had to build a parser, implement a state machine and a few other things. All in Haskell.

For my master's I took a course on static analysis, for which we had to perform usage analysis, type error diagnosis, implement a type checker etc. All in... Haskell.

We did something similar, not in Haskell unfortunately. We did have a programming languages class that introduced us to haskell. It seems so damn intuitive. As a web developer though there just isn't the support for that language unfortunately.

I went through the joint honours degree in mathematics and computer science at Oxford (that's basically a particularly rigid double major for people unfamiliar with the British system). I did not learn C, mostly because I spent a good deal of effort trying to stay as far from actual implementations as possible, but I'm sure it's quite possible for even straight CS students to not learn C. I don't believe that any required courses (which in particular does not include a course on operating systems) use C.

The ones that matter do.

If a CS/Engineering program doesn't have an OS class with non-trivial labs in C, it's simply not serious and a red flag on a resume.

I looked over the degree requirements for an MIT 6-3 (Comp Sci part of EECS) degree and it looks to me like you can get one without taking a course in C. Maybe MIT EECS "doesn't matter", but I doubt that.

Peeking at the course required[0], it's hard to avoid microcontrollers.

Furthermore, 6.004[1] looks like it has to involve C at some point.

[0] http://catalog.mit.edu/degree-charts/computer-science-engine...

[1] http://catalog.mit.edu/search/?P=6.004

You are probably my least favourite poster on here, but I agree with you here.

Reply on news.ycombinator.com