Or so says the 2017 IEEE Spectrum ranking, published this week.
IEEE Spectrum, a publication of the The Institute of Electrical and Electronics Engineers, a technical advocacy organization, says it evaluated 12 metrics from 10 sources to arrive at this conclusion.
It claims to have culled data from Google Search, Google Trends, Twitter, GitHub, Stack Overflow, Reddit, Hacker News, CareerBuilder, Dice, and its own digital library.
Why is Python such a popular language??
The syntax seems designed to make mistakes in.
What kind of mistakes? Tabs vs spaces? Well, yeah, that's hard to spot, but no one uses hard tabs anymore anyways. Right?
It's a language designed to make complicated things easy for idiots. And modern college kids most certainly are idiots. They start crying because they don't know where the missing closing parenth goes in a single-nested if statement.
Guido van Rossum created it because his kid wouldn't stop crying during his programming lessons. Shut the little fucker up, you know?
TIL: EF is more of an idiot than anybody thought!
** I know I know, some of you may claim you knew EXACTLY how much of an idiot he is, but c'mon, the answer is "endless"
Stop the presses! Stupid person makes stupid comment. Again.
Web celebrity thought-leader Randall Munroe told code monkeys to code in Python, and they fucking do as they are fucking told. There are only two paths in the world: The Trend or death.
Ram-Hole Man-Ho admits he's a lucky fucking asshole:
Never stop reading XKCD, no matter what anyone tells you.
Haw. My seething hatred for Randall knows no bounds. Regarding the first link, it makes sense that the coward gets his highs from DXM and wine coolers because he's too much of a pussy to handle liquor much less real psychedelics.
I have worked with many scientists and engineers throughout the years, and the handful who studied physics (as opposed to math/compsci/engineering) in college were extremely mathematically capable but otherwise autistic retards.
Randall has you all figured out.
Physics tells us that negative reviews are really just positive reviews from people traveling backward in time.http://www.xkcd.com/1869/ [xkcd.com]
Physics tells us that negative reviews are really just positive reviews from people traveling backward in time.
There's a spit of reason there. After all, you'd be hard pressed to find anyone suggesting Ethanol-fueled is moving forwards with the times.
I have worked with many scientists and engineers throughout the years...
Yet not even a bit of their smarts rubbed off on you. You do know that learning doesn't stop when you leave school, right?
Two of the Python language's design tenets:
Errors should not pass silently.In the face of ambiguity, refuse the temptation to guess.
Errors should not pass silently.
In the face of ambiguity, refuse the temptation to guess.
It's a language where programming errors tend to express as exceptions, instead of silently doing the wrong thing. Which means you get a chance to fix it, and a traceback text that very often points you at exactly where the error was made.
I don't know what it is about Python's syntax that makes you make mistakes, but for me it's a language that helps me produce robust code.
Usually when I see that sort of language, what the person is actually trying to say is, "I can't copy-paste my code from one place to the other and it still works." While that is true, because Python uses white space to denote most blocks of code, it is also true that the same things can happen in languages that use braces. Sure, Copy-paste of a simple if block is more likely to be a problem in Python than other languages, but there are other constructs that will get you in more trouble being copy-pasted in other languages than Python.
The real problem is that people need to not blindly copy-paste, regardless of the language.
I didn't realise "errors should not pass silently" was an explicit part of Python's design. Aside from the whole indentation thing, what we could term "silently introduced errors" is what trips me up again and again when using Python.
object.color = 'red' # do something else for a while object.colour = 'blue' print object.color
Autovivication. The gift that keeps giving. (The program prints "red", by the way - as it should, but it probably wasn't what the programmer expected.)
I find myself using spell-check on variable names (!!) a great deal when programming Python! At least in Perl, when autovivication ceases to be useful (in programs longer than a few lines), a simple "use strict;" at the top expunges that entire class of mistake.
It's a language where programming errors tend to express as exceptions
Which is sort-of-cool, but in many cases I'd prefer an error at compile time. Exceptions are nice but I don't want to have to manually hunt down every logic path to find all my stupid mistakes.
I love Python, idiosyncrasies and all. Van Rossum has been very clear about documenting Python's behaviour and rationale from the start (doesn't mean I always agree with him) but at least the contract is clear. And when I shoot myself in the foot, as I do on a regular basis when writing Python - like that sample above - I laugh and think "did it again, you fool, eh? At least it only cost a couple of hours."
Well, you could always use one of many static analysis tools for Python programs. Most will catch that specific error, due to an initial assignment outside of __init__ or thinking you are missing a property decorated function definition. A quick run through a test suite or bytecode compilation (PYCMD -m compileall -fq -j0 -d /tmp INPUT_DIRECTORY) will find many as well. Also, if you have a problem with indentation (PYCMD -m tabnanny INPUT_DIRECTORY) can catch many of those as well.
Several very large companies and industries went all in on it. I mean toss out all the other langs and use ONLY python. They are all realizing it was a terrible error at this point though. As it was not the language that was their problem but the culture they had for coding.
Python is pretty good at the 'medium' program as I call it. A 100-2000 line bit of glue code. Outside of that it usually collapses on itself because it does not have strict typing and mediocre speed. So you spend a lot of time managing the language instead of managing the problem. C has a similar issue with you end up managing the memory instead of managing the problem. There is no good 'fix' for those issues. So we make due and re-invent new languages thinking 'we got it this time' (rust/go).
My real issues with python. One the spacing issue. It is dead easy to create a scope problem. The non typing of variables. You can ducktype into bad problems and not even realize it until your QA/end user is saying xyz is crashing. The mentality of shorter is better. So you end up with semi cryptic bits of code that are not 'faster' but certainly are much more clever. We also have 2 versions of python 2 and 3. It is not clear what we should do. When ambiguity reigns people get antsy.
Do I stop using a language because of that? No. I work on the problem at hand.