Python Is On the Rise, While PHP Falls (dice.com)
Nerval's Lobster writes: While this month's lists of the top programming languages uniformly put Java in the top spot, that's not the only detail of interest to developers. Which language has gained the most users over the past five years? And which are tottering on the edge of obsolescence? According to PYPL, which pulls its raw data for analysis from Google Trends, Python has grown the most over the past five years—up 5 percent since roughly 2010. Over the same period, PHP also declined by 5 percent. Since PYPL looks at how often language tutorials are searched on Google, its data is a good indicator of how many developers are (or aren't) learning a language, presumably because they see it as valuable to their careers. Just because PYPL shows PHP losing market-share over the long term doesn't mean that language is in danger of imminent collapse; over the past year or so, the PHP community has concentrated on making the language more pleasant to use, whether by improving features such as package management, or boosting overall performance. Plus, PHP is still used on hundreds of millions of websites, according to data from Netcraft. Indeed, if there's any language on these analysts' lists that risks doom, it's Objective-C, the primary language used for programming iOS and Mac OS X apps, and its growing obsolescence is by design.
We won't want this Dice shit here.
Is there really no one at all willing to buy Slashdot?
Which seems highly questionable. Seems to me the methodology of using google search metrics for language popularity works to gauge popularity of a language with enthusiasts but not of actual commercial projects.
PHP depresses.
It is official; Netcraft now confirms: *BSD is dying
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming close on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a cockeyed miracle could save *BSD from its fate at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
Counting the number of times tutorials are accessed tells you how many people are learning (or considering learning) a language, not how many are using it now. All this can do is tell you if people expect to need it in the future, because for the most part, if you're currently programming in a particular language, you shouldn't need to be going over tutorials.
Good, inexpensive web hosting
What about Swift? Considering it's only 2 years old, surely it's grown by the most, percentage-wise. I suspect a company called PYPL has an interest in promoting Python...
Python? Seriously? The language where I can't cut and paste anything without it seriously being broken because... whitespace matters?!
Python is as dumbass does.
I got your Python, right here.
You are welcome on my lawn.
Isn't it kind of a strange metric? It measures people who don't really know the language but want to learn it. But did they learn it in the end? Did they end up using it? Was it actual programmers trying to get into a new language / refreshing one for a new project, or was it complete beginners who heard "python is cool" or something like that and search for a tutorial thinking they will be great programmers?
And not all languages have an equal basis in this metric. For example who would search google for a perl tutorial? I mean it doesn't even support regex for christ sake! Also it is well known that Perl either comes as an Epiphany, or you are taught by Monks, you don't read a tutorial...
Violence is the last refuge of the incompetent. Polar Scope Align for iOS
Python provides no true concurrency due to global interpreter lock. Java is not suitable for realtime due to unpredictable GC, while C/C++ is not suitable for anything which should never crash or return random results due to memory corruption. None of mainstream languages make automatic use of multiple cores and GPU - explicit provisions must be made by programmer to parallelize part of the program, often with error prone semantics and a separate language like OpenCL.
Yes, those are hard problems, but it's also 2015 and we can come up with powerful compilers and JIT virtual machines. Going back to less concurrency than plain old shell scripts where '&' starts a true separate process is not an answer.
If religious wars are worth the time, then have at it.
I'm tired of this shit.
It's all those googling to figure out how to fix their white-space messes
I know it's a matter of taste, but I understand why Python, aside from simply being popular, is used so often. Having spent time using several languages, I can say that brevity bordering on the obscure (often mistaken for elegance) is not something to encourage. Don't get me wrong, it's great if you can reduce the steps used to implement an algorithm (especially if you get big-O benefits as well), but simply reducing line counts isn't anything to brag about. I mean, who cares if you implemented something in a single line of Perl that took 5 lines of Python for me? Eighteen months later, when the code gets dug up for whatever reason, I know which will be far easier to follow and correct if needed.
That, to me, is the real strength of Python: it enforces readability without requiring too many extra characters (Tcl being representative of the other extreme). If using an interpreted language isn't an issue, it almost always seems like the way to go for my tastes.
We will never be the change to the weather and the sea
No real programmer uses these stupid script kiddie languages.
I repeat, "Whoopdee fucking doo", which means, "Who fucking cares?"
Just cruising through this digital world at 33 1/3 rpm...
I got your Python, right here.
I've got a cock a NIGGER would fucking ENVY. I bet it could disappear all the way up your SHIT ENCRUSTED ASS HOLE!! OOoooohhh yeah baby, that's the stuff!
Hello,
Although python is efficient you cant downgrade php, because php is used in all most popular solutions. even today.
Abdul
www.shortreminders.com
So, the fact that people who are forced into programming in Java spend more time (out of necessity) googling for tutorials than they do writing code means that Java is the most popular language?
Java, Python, &or php are some of the most common starter languages; once an amateur has a couple of them down, they're better at finding tutorials by going straight to sites that host them - without the intermediary Google search.
Didn't Slashdot just run a post about how WordPress (written in PHP!) powers 25% of the web?
Why, yes. Yes, they did.
Please stop the hyperbolic clickbait.
Perl. Perl all the way through, and nothing but Perl. Apparently after they canned the guy who took credit for writing it, they didn't feel it was worth while to put any additional money into the code, ever again (and it seems that attitude has continued through subsequent acquisitions).
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
PHP is my language of choice. Yes the language has issues, but it's almost always able to get the job done in the least amount of time - plus it works in so many different environments.
It makes coding fun, especially for prototyping and playing around. Not to mention I code circles around the Java and C# guys at work.
(Otherwise, I'm all about C)
Come get your white space.
Because of the duck typing maintaining, extending and refactoring any non-trivial Python project is a fubar. Make a typo in the variable name and catch this bug 2 months later in the production deployment. Thank you very much, but no unit tests from the whole world will cover this.
Because of the GIL it doesn't scale across the modern hardware so it forces programmer into process-level parallelism and 3rd-party http server with wsgi crap which gives deployment and maintenance headaches.
Because of the interpreting nature it is too slow to be considered as good choice for any CPU-intensive tasks (not only math but anything outside of I/O and networking).
I must admit though that it is great for scripting. So there should it stay forever and personally I'd run away from any job description which includes Python as a primary language.
You forgot to ask whether he'd like fries with that.
You forgot to wipe that extra cum off your chin from the nigger penises you love to suck. There is also a thin layer of your own fecal matter on the outside of your mouth because you love it when the niggerdicks fuck you in the ass (using their large girth and your blood for lube) and finishing in your mouth with a nice money shot.
Verbose notions of readability are misguided. Every time someone discourages brevity and says that something takes 5 times as much code but is more "readable", I wonder how they haven't noticed the unnecessary time and mental energy they are wasting.
The only way to get 5 times the LOC is to have more state to track across those lines. You could argue that a single line 5x as long due to having mnemonic names is clearer than one with just a,b,c or whatever, but 5 lines vs 1 line means you have 4 statements through which you have to track the names and meanings of symbols before you can understand the ultimate line. That is not more readability, that is overhead. That is taking up space in your short term memory (which has real, physical limitations).
If you are walking down the street and accidentally kick a stone, you will find that underneath that stone there was a guy programming in php... They are everywhere these days.
Index is created by analyzing how often language tutorials are searched on Google
And how should this be related to rise and fall of a programming language popularity?
I would instead say that it shows how hard a programming language is to be learnt or mastered.
This study is completely flawed and aimed to religion wars among programmers!
Every one actually knows that C is the king of all languages, you insensitive statistical clod!
Sent as ripples into the electromagnetic field. No single photon has been harmed in the process.
I know my comment shows up a bit late but I just started re-learning Perl5.
I have a well valued history in programming different languages. Assembler, C, Java and Scripting. The past years I did a lot in Bash to save a lot of repeated command line hacking when I needed to enter always the same stuff.
A few of my projects reached a nice amount of wrokflow (and size: 25k bash). And thus I decided to have a few changes here. In the 90's I was told that Perl replaces Bash, AWK, SED, Grep and co. and thus the people who told me where right.
I sat down and made some thoughts which way to go. Perl and Python came into my mind. Sure Python seem to have some adantages as well because it seem to be more mainstream. But at the end I settled with Perl because Perl is what I wanted.
If you compare the scripting features then it's this Bash for basic stuff, Perl and Python for more advaned followed by all the modern (or more complex) Languages like C or Java.
After reading the book "Beginning Perl" from Curtis Poe, I started to realize that the language has indeed a "different" syntax. Datatypes are dealt differently. Scalars, Hashs and Arrays etc.. I came to the point where I tought if the code is portable to something else one day. E.g. if I switch from Bash to Perl to e.g. Java.
But then. It's always up to the programmer to write clean code.
The reason why I didn't went the Python way... Because everyone is jumping on it... It makes one become one of many people...
In the UK at least Python is being taught in secondary schools (ages 11 to 16) this could account for a lot of tutorial searches.
How about you fix the terrible PHP parser so it isn't TRIVIAL to write unsecure code?
Don't give me your bullshit about how it is easy to avoid that problem, you are not the reason this is a problem, the other 70% of the users that use PHP are the problem. The amateurs that google some morons stackoverflow post, or some shit blog post on a REALLY NEATO piece of code that leaves their website open for attack with automated tools.
Literally no other language has the problems PHP does at the level it does. PHP is KING of being broken by design. FIX IT.
For all the things PHP to be "dying" to, it had to be Python.
For a start, those people are probably trying to figure out why the hell their code isn't working because they thought whitespace was a GRRREAT way to enclose code in distinct groups, be it functions or whatever.
Seems really objective. And they're using Google search results as a metric. We all know Google is a Python/Java shop. Java at #1, followed by Python "on the rise". No surprise here.
The object oriented system of perl 5 can not keep data hidden. There is autovivification, and other crazy stuff possible with perl 5.... Knowing the entire language requires lots of constant work to keep it in memory.
Python and PHP have two completely different use cases. They're not related at all. Your implication is absurd.
I knew this was going to happen the moment that teenage chic on the episode of Blindspt last week started dissing the FBI chic over using PHP.
"A person is smart. People are dumb, panicky dangerous animals and you know it." - K
what about Fortran? Should I learn Fortran?
you can't just take a stock ticker and make it your website's name. PYPL?
It seems to me that an increase in the people attempting to learn Perl could be just a side effect of them trying to learn another technology. Take Hadoop into consideration, if I'm a developer attempting to learn Hadoop I can learn Java or Purl to complete the same body of work in Hadoop. There are also parts of Hadoop that uses functional programming which wasn't supported in earlier versions of Java so they needed to look at Purl to support that aspect of the architecture.
Java has been doing realtime for over a decade now. In fact the very first JSR was JSR 1: Real-time Specification for Java which began in 1998.
Saying Java is not suitable for realtime due to "unpredictable GC" shows you haven't read much on the topic. Many Java open-source projects guarantee millions of operations per second on the right hardware. Java has a huge HFT community footprint.
Take a look at what http://chronicle.software/ and OpenHFT is doing for instance.
Some languages are better than others for certain tasks, and some languages, like PHP, are crap. While there are things that PHP will do better than C++, there's basically nothing that PHP will do better than Python.
Likewise, I can think of no case for staring a new project in COBOL.
Democracy Now! - your daily, uncensored, corporate-free
You forgot to check your fail.
Il n'y a pas de Planet B.