Stack Overflow Reveals Results From 'Largest Developer Survey Ever Conducted' (stackoverflow.com)

More than 64,000 developers from 213 countries participated in this year's annual survey by Stack Overflow -- the largest number ever -- giving a glimpse into the collective psyche of programmers around the world. An anonymous reader quotes their announcement: A majority of developers -- 56.5% -- said they were underpaid. Developers who work in government and non-profits feel the most underpaid, while those who work in finance feel the most overpaid... While only 13.1% of developers are actively looking for a job, 75.2% of developers are interested in hearing about new job opportunities...

When asked what they valued most when considering a new job, 53.3% of respondents said remote options were a top priority. 65% of developers reported working remotely at least one day a month, and 11.1% say they're full-time remote or almost all the time. Also, the highest job satisfaction ratings came from developers who work remotely full-time.
62.5% of the respondents reported using JavaScript, while 51.2% reported SQL, with 39.7% using Java and 34.1% using C# -- but for the #5 slot, "the use of Python [32.0%] overtook PHP [28.1%] for the first time in five years." Yet as far as which languages developers wanted to continue using, "For the second year in a row, Rust was the most loved programming language... Swift, last year's second most popular language, ranked as fourth. For the second year in a row, Visual Basic (for 2017, Visual Basic 6, specifically) ranked as the most dreaded language; 88.3% of developers currently using Visual Basic said they did not want to continue using it."

Comments

Using Javascript

[phantomfive]

Those poor programmers using Javascript. What a lousy language.

(If anyone wants to know why, I will pick one feature out of many. Say you wrote a large program in Javascript, which is happening more often these days. Then you want to refactor by renaming a variable. In Java or C or C# you can refactor by using an IDE automatically, and if somehow you miss an instance, it will be caught at compile time. In Perl or Objective C or Smalltalk, it will caught at runtime in the worst case. But in Javascript, it might not be caught even at runtime, and instead will just cause strange behavior).

Re:Using Javascript

[BarbaraHudson]

Javascript variables are the way they are so that you can use them on the fly without having to pre-declare each and every variable along with it's type which is a god send not a problem.

If you think that's not a problem, you're the problem. :-)

Re:Using Javascript

[phantomfive]

Plenty of IDEs can already handle this without much of a problem, and as I said, Google closure already does static code analysis which will probably catch any "bad" refactoring you've done.

It's not clear you've understood the problem. The bug is syntactically and semantically correct, so static analysis will not detect it. It's only manifests itself as a behavioral problem. Please try to say something that indicates you understand the issue (if you choose to again reply).

Re:Take the survey with a gain of salt

[BarbaraHudson]

Yeah, statically typed languages look overwhelming/verbose and take more time to type and plan out

That nasty "planning" - there's no time for it in today's culture, where everything is just thrown together after a few "planning sessions" that are basically verbal diarrhea pushed by "big vision" marketing and bosses who may have had a clue in the past, but don't any more and are flailing about to find some project to justify their jobs, same as almost everyone else chasing the big-money exit strategy dream instead of doing the hard stuff like, you know, planning.

The whole "vision thing" has turned software into the cesspool it is today.

To summarize

[somenickname]

To summarize, a bunch of dime-a-dozen web guys, who rely on stack overflow for every other line of code, have declared that they are underpaid. And, they would prefer to work at home so that if someone asks them a hard question, they can ask it on stack overflow before answering.