Slash Boxes

SoylentNews is people

posted by martyb on Saturday August 05 2017, @03:47PM   Printer-friendly
from the ALL-programmers-know-profanity dept.

Among developers, Python is the most popular programming language, followed by C, Java, C++, and JavaScript; among employers, Java is the most sought after, followed by C, Python, C++, and JavaScript.

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.

Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Saturday August 05 2017, @10:49PM

    by Anonymous Coward on Saturday August 05 2017, @10:49PM (#549265)

    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.