Python Bumps Off Java As Top Learning Language
itwbennett writes: Python has surpassed Java as the top language used to introduce U.S. students to programming and computer science, according to a recent survey posted by the Association for Computing Machinery (ACM). Eight of the top 10 computer science departments now use Python to teach coding, as well as 27 of the top 39 schools, indicating that it is the most popular language for teaching introductory computer science courses, according to Philip Guo, a computer science researcher who compiled the survey for ACM."
not will but it is
could have been worse, it could have been javascript
2.x or 3.x?
Finding God in a Dog
I can't wait for this generation to saturate the industry. Fewer bugs, better features, from less nonsense to code programs with. They might even be better as people, with clearer heads. Python might even help you think more clearly.
"Top Learning Language" ...OR... "Top Teaching Language"?
Do we have some great metrics as to how well people taught in Python actually *learn*? You know, for things like memory allocation, pointers, and so on?
Python is an awesome language for learning - I'd vote for any language that allows interactive code debugging and experimentation. I see Python used everywhere these days so it's even useful as industry experience.
I'm a C++ programmer by trade but there's no way I'd wish that language on a student. It's a hellish nightmare clusterfuck language that doesn't know what problem it's trying to solve anymore. Java is loosely based on C++ so it inherits a lot of the problems. I only wish Python would allow stricter interface constructs...
It makes sense. IMHO python removes a lot of the hardware considerations that other languages have. This allows for a focus on the CS material, rather than the engineering material. An advantage over java is that it also supports functional programming. That means that you can teach introductory CS principles in multiple programming styles without having to switch languages. Top it all off with forced indentation (not my favorite thing), which makes beginner code easier to read for instructors and I can see why they did this. Now, later they'll get into asm and C/C++ and memory alignment and paging and all that stuff, but starting out it's nice.
Eat sleep die
If you didn't want to learn programming languages, why are you taking computer science courses?
If you're being force-fed anyways, I think python would be much easier to stomach than java for introductory courses. And it would be much easier to grade (if grading consisted of more than "did it output correctly") since introductory students aren't exactly known for their exceptional code organization and formatting skills.
Lots of people hate the whitespace block-delimiting, but I think Python is *way* better than Java for beginning programming classes.
I've seen the transition my alma mater made, between Modula-2 and Java. Modula-2 is trivial to pick up for anybody who cut their teeth on Turbo Pascal or Delphi, and "hello world" is quite easy to explain to anybody otherwise unfamiliar with programming. Try repeating that trick with Java's equivalent, and you'll understand why first-year dropout rates skyrocketed upon the switch. Anyway, Python has some nice goodies in the language which lends itself nicely to teaching both OO, and functional styles in the one language.
I've even seen this in non-IT specialties; at Imperial College here in London, the newbies learn Python (stands to reason, because it's the weapon of choice for many scientists, especially physicists). King's College, OTOH force their first-years to take a unit of Fortran, which actually manages to be about fifty times worse than any other language I've attempted to use.
The steepness of the learning curve is critical AFAICT -- you don't want to spoon-feed kids, but you don't want to crush them in their first two weeks at college either.
now I guess python will be forced fed to people who don't want it
That seems like a silly objection. It is not practical for a teacher to let each kid choose their own language, nor are the kids knowledgeable enough to choose. I don't see any big organizations pushing Python the way that Sun was hyping Java back in the late 1990s.
At my kids' school, they start teaching programming in 4th grade, using Scratch, and move to Python in 6th grade. It seems to work well.
java was only "the most popular" because it was force fed to people who didn't want it.
I don't think you understand how schools and their curriculae work. Nobody is holding a gun to the collective and independently-operated heads of CS departments to demand which language they use for beginner courses.
Java was historically chosen because it was a safe option; used widely in industry, decent documentation and tools, it supports good programming practices, and it provides reasonably powerful options while being relatively beginner friendly. Java largely replaced C and C++, which are not beginner friendly.
Computing science is not about programming, but programming is often used as a tool in computing science and they therefore (rightfully) have you take programming courses before going into the more theoretical material.
That means I have to REALLY step up my Python chops if I want to compete.
Finding God in a Dog
Wait!!! What happened to Pascal?!?!? On a more serious note, Pascal was the premier teaching language back in the day, but it really wasn't used much in the real world. It was a stepping stone for learning C, which is where the real power was at and what "real" applications were developed in. I believe there is less disconnect today between the popular learning languages and what is actually utilized in the real world.
Better known as 318230.
It doesn't have pointers, but it does have references - which are basically pointers without arithmetic. In fact, in Python, everything in a reference (even primitive types like int are reference types). This is sufficient to explain the core notion of indirection, and data structures built on that notion, like linked lists or binary trees.
As much as I hate whitespace formatted languages I hate Ruby most of all. The language itself isn't the problem, it's the hipster asshats who promote it. They should all die in a fire. I'm working on master's in CS and we still use Java, C, and C++ so it's going to be a while before any of the decent languages are displaced in academia.
be capable of comprehending blocks. Their kind simply doesn't fucking get begin and end even in pseudo code. I've had to fire three Python devs that simply couldn't figure-out how to use {} in JavaScript. It's not that hard, but I think that horrible language spoils them into thinking that whitespace is magical. Of course colleges want to graduate people that can't keep jobs so they get more customers for their masters programs so they love Python. Making sure you graduate people that are unable to find and/or keep jobs is the number one job now of college professors.
And even most C64 owners dropped it ASAP and went straight for assembly.
Which only has equivalents to goto and gosub.... you were saying?
"His name was James Damore."
No, it is popular because, despite a good many flaws, it remains the best cross platform solution we have.
The world's burning. Moped Jesus spotted on I50. Details at 11.
Python isn't a bad first language. It has all the important advanced concepts - objects, dictionaries, closures, and threads. The syntax is reasonable. Some people are bothered by the forced indentation, but for new programmers, it will seem natural.
Most of the problems with Python are performance related. They come from obscure features of the language, such as the ability to do "getattr" and "setattr" on almost anything, including objects running in another thread. So everything has to be a dictionary. (This is sometimes called the Guido von Rossum Memorial Boat Anchor.) PyPy is struggling hard to overcome that, with some success. (The optimization approach is "oh, no, program did Obscure Awful Thing which could invalidate running code" - abandon compiled JIT code, shift to backup interpreter, flush JIT code cache, execute Obscure Awful Thing, wait for control to leave area of Obscure Awful Thing while in backup interpreter, rerun JIT compiler, resume running compiled code.)
C is very beginner friendly in my opinion. It was my first non-BASIC language. Learning C you learn how those bits and bytes work and how shit gets done. The paradigm is old but not obsolete.
But yes, Python is a great choice. My only gripe is the use of indentation instead of curly brackets to mark blocks.
Comment removed based on user account deletion
Digging further than the fine article to the blog that it was based on. It appears that the methodology of the study is wrong for what it purports. There were multiple languages and courses from each school; It speaks as if this is the intro for CSC majors, and then adds CSC courses that wont go towards a CSC degree; I.E. programming for engineers with matlab at Georgia Tech for example.
The overwhelming majority of CSci graduates that I have known started undergrad by learning Scheme. IIRC that language was actually built for the purpose of teaching the fundamentals of programming. Why was it replaced (beyond the fact that hardly anyone in the real world uses it)?
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
Back in 2001 I was attending Minnesota State University Mankato. The CS program there did all of the introductory programming courses in Python. A year or two prior to my enrollment all the intro classes were taught in Java. The profs found that students would get hung up on java syntax when their goal was to teach them basic programming concepts so they switched to Python. Courses in Python only lasted for a couple semesters. After that the rest of the curriculum was primarily taught in Java. I think that Python accomplished the CS department's goal quite well.
Our bugs are smarter than your test scripts.
You are far from alone in misunderstanding Javascript.
Verbum caro factum est
Or the much better programming construct 'comefrom'...
Non-Linux Penguins ?
Python has a number of nice features for the beginner programmer.
1) It is easy to learn
2) It has a REPL.
3) It has a large standard library, and most things things in the library are easy to use.
The library is not super abstracted and overly engineered like so many other tools.
4) It has a large universe of third party libraries that are useful and easy to install.
There are bindings to many C/C++ and Fortran libraries. Things like numpy, scipy, and matplotlib.
5) The language and its libraries work on Windows/Linux/Mac.
6) The language is good at allowing one to focus on the problem at hand without worrying so much about minutiae of the language.
7) It supports imperative and object-oriented programming and has some support for functional style programming with map, filter, lambdas and list comprehensions. The functional programming support is on the weak side, but at least there is something.
The language also has some down sides.
1) Python hides low level details from the programmer. As a student learning about programming, ones needs to understand this stuff. Thus 'C' should also be taught.
2) It has been my experience that dynamic typing is useful for relativity small single person tasks. Somewhere around 30,000 lines, one begins to wish for static type checking. However, one needs a good type system. The rise of generics has greatly improved modern statically typed languages.
After reading "Learn You a Haskell For Great Good", I think all programmers should learn Haskell.
It is not really just about learning Haskell either, but understanding the power of function abstraction, combinators, referential integrity, organizing data, and managing side effects.
Java is also nice in that it was part of the C syntax family. If you know Java, it is trivial to switch to C# and moderately easy to switch to C++. C is different enough to cause grief, but people do catch on to functional languages and memory pointers.
I learned Visual BASIC during an early CS class. Wasn't really able to make much from that and apply it towards other languages. Also learned Perl during an early CS class. It was so alien from other C syntax languages (and most other languages in general) that I also couldn't apply it toward other languages. They were interesting languages to learn and I did pick up some knowledge regarding general programming, but I think I gained a lot less than had Java been one of my first CS course languages.
My only gripe is the use of indentation instead of curly brackets to mark blocks
I'll never understand that criticism. Don't you indent your code? Have you ever been fooled by incorrect indentation that didn't compile the way it looked? Brackets, begin..end, and semicolons are crutches for compiler writers not programmers.
Yeah, because the concepts of C# cannot be aplied to any other language like Java or Python.
Oh, right, I thought that JavaScript sucked because I was under the impression that it was dynamically typed, allowed monkey-patching, had a lame set of numeric types, poor support for sequential I/O, etc., etc., etc. Oh, wait... those things are true? But Douglas Crockford says it's Lisp-y, so that gives us license to sweep all those problems under the rug.
And for that reason python is good for a first course, as it forces the students to indent. I am tired of lazy students that don't indent, and then complain why their code doesn't seem to follow the intended flow. It is hard to teach good habits and practices. And any help, specially from the programming languages, is welcome.
That's rubbish. Most of the major platforms have had Java ported to them. Including various obscure systems is ludicrous. If I want a program that I'm almost guaranteed will run without recompile on Linux, Windows, BSD and even many mainframes, then Java remains the best solution. I'm not saying, from a programming perspective, that it's all that great, but from a platform neutral perspective for most of the systems that a programmer will encounter, it remains the best.
Have fun running an x86-64 Linux binary natively on a Windows 8 machine. I can. however, write a Java program that I can almost guarantee will in fact run on x64 Linux or Windows.
The world's burning. Moped Jesus spotted on I50. Details at 11.
Have you ever been fooled by incorrect indentation that didn't compile the way it looked?
Nope. My editor takes care of indentation for me, in every common language except Python, and when I have to deal with a batch of code written by someone else, I run it through indent(1) first. So, in fact, it's just the opposite: when the indentation doesn't match what I expect, I know there's an actual problem in the code!
With Python, on the other hand, I'm actually more likely to have an error in the indenting, because there's no easy way to see how many blocks I'm terminating when I outdent by an arbitrary amount. Which is a real PITA when you're refactoring.
Of course, things may be different if you're using crappy tools. But professionals shouldn't be using crappy tools.
Brackets, begin..end, and semicolons are crutches for compiler writers not programmers.
No, they're tools to make my job easier. Whatever the historical reason for them may be, they benefit the programmer! They make me more productive.
Now, I'll grant that Python is a remarkably good language despite its horrible flaw of relying on indentation. And many of its good features also make me more productive. But that doesn't mean that relying on the indentation isn't a horrible flaw.
Pascal, named after one of the great thinkers of his era.
Python, named after people with silly walks.
Python lets you dive in quickly, and it has two properties I like in a first language: It encourages good practices, and it's in the C-derived language group so what you learn transfers easily.
The only thing you lose with Python is some of Java's ability to do "real" programming directly. A kid can use Java to do Minecraft modding, and a college student can write Android apps. There aren't so many direct uses of Python. (Yes there are a lot of real-world uses for Python, but not for writing user-level apps.)
My recommendation for an initial language has long been Pascal. Technically, it has nearly all of the big concepts that you'd want to demonstrate in a computing language. Practically, it is sufficiently annoying that the student will be receptive to the idea that the language of a program is a design choice rather than getting stuck on the first thing they learned.
what do you mean, picking up steam - Enterprise (those who are Windows shops of course) use C# extensively.
However - think of it like this. Ten years ago, you'd be the one saying Visual Basic is the most widely used language in enterprise, so we should be teaching kids that. And today, those kids would be coming out of college knowing all about VB6 (note, schools don't change curriculums overnight, it takes a long time for them to realise, and even longer to implement change - Java was popular in 1996 which is when it started to gain traction in university departments).
So, I hope this shows you the fallacy of teaching using "what enterprise wants now". You need to teach what will stand the kids in good stead for the future, that teaches them fundamental programming concepts that they can use their knowledge to apply to other languages. Personally I think they should teach a language that no-one uses in industry. Pascal (or Oberon) or something dedicated for teaching.
Oh, and that only applies to Windows shops, non-windows people don't use C#.