Undergrads are stupid? Blame the universities for teaching C and Java

https://archive.rebeccablacktech.com/g/thread/61460559/
/g/ is where CS undergrads hang out. The quality of knowledge of /g/ reflects the quality of their education.

In Brazil you have C in introductory classes, second semester is C and assembly. Why are american CS classes such a joke?

The only way to teach someone properly is:
>pseudoassembly language to make the students get the basic principles of how a computer works (without introducing any platform specific stuff)
>C, to teach basic imperative programming and also memory-related matters
>modern C++ for introduction to OOP, templates etc, and also to make the students understand that automatic memory management is possible without a garbage collector
>a modern OOP language (C#, or possibly Java)
>a meme piece of shit scripting language (most likely Python)
>a pure functional language (most likely Haskell)
>SQL, an actual assembly language and webshit languages (Javascript, HTML, CSS) somewhere along the way

This way you get the full picture, a thorough understanding, and you do it in the proper ascending order of abstraction from the hardware layer.
That's what my university did in my CS course, and it was worth it.
And this order makes retards fail quickly, so here's another upside.

I like Java, its the comfiest language. But I wouldn't trade having my 101 class in C for anything. I believe it was a very valuable experience. Plus, it helped me with OS, Systems programming, and computer architecture later on down the road. Not teaching C just fucks students over later. Maybe it's for the best though cause ee need less JS script fags scraping out a CS degree and calling themselves developers anyway. Stallvolution will eliminate them from the equation.

As a CS major who was taught Java first then C and C++ later. Java was easier to learn, but I wish I was introduced to the complexities of C first. One big thing that I can think of is that Java has a garbage collector so you are basically allowed to write shit code. Once we started learning C, that shit wouldn't fly and the idea of memory allocation was lost on many.

C might be harder to learn, but for CS it's a better foundation imo.

>>11

The more popular a language is, the more that happens. So this isn't a fault of C.

C questions are by smart people bewildered by bad design and limitations in the language and the answers defend this bad design.

Another LITHPer who thinks sexps are the pinnacle of good syntax.

I don't think Sexps are good syntax but I think C is bad too. C is hard to learn compared to what it has and not because of the concepts, but because of the syntax and semantics. Pointers are not hard to understand, but C's pointer syntax distracts you from what pointers are. C programmers ask about whether it should be int *p or int* p, which has nothing to do with pointers at all. int* p, q isn't about pointers either. If * meant ``constant'' or ``lazy evaluation'' there would be the same problem because it's a C syntax problem, not a pointer problem. Good syntax helps you understand things better and makes these questions unnecessary.

C's switch is another bad design. You won't know why unless you compare it to other languages.
http://www.ada-auth.org/standards/12rm/html/RM-5-4.html
http://www.freepascal.org/docs-html/ref/refsu56.html
http://www.freebasic.net/wiki/wikka.php?wakka=KeyPgSelectcase
http://www.cs.mtu.edu/~shene/COURSES/cs201/NOTES/chap03/select.html
http://documentation.microfocus.com/help/topic/GUID-0E0191D8-C39A-44D1-BA4C-D67107BAF784/HRLHLHPDF903.html

These are easier to learn, more powerful, and a greater benefit to the programmer.

In a C class, they would be talking about fallthrough and why cases are only limited to single integers instead of understanding why this kind of control structure is useful and improves program readability and optimization. Stack Overflow has questions about why you can't use strings and floats, but there are programming languages where you can use strings and floats in a case or select statement and most of the answers don't mention that. That's how people are dumbed down.

Free market

But who created the supply of CS grads who only knew Java? Why did companies need to hire Java programmers when there were no Java programs?

It's just an introductory.

It should be an introduction to programming, not an introduction to the bad design of a particular language.