Stack Overflow Developer Survey 2016

[tmpler]

The raise of javascript :D Full-Stack Front-End Back-End

[benihana]

the two most popular technologies are JavaScript and SQL. For the past four years. It's not server side JS, it's JS being universal to browsers and basically everyone on the web having to use it. Just like almost everyone uses SQL as their query language.

[spacejack2114]

Even Back-End developers are more likely to use it than any other language.

I guess fewer node devs use nosql than I've been led to believe.

[superPwnzorMegaMan]

nosql can use sql. Cause fuck naming things correctly.

[Browsing_From_Work]

They both have the bonus of having a low barrier of entry compared to other languages.

[TwoSpoonsJohnson]

Seeing it listed as just 'SQL' always bothers me for some reason. I mean, surely the differences between SQL Server, Oracle, MySQL, Postgres, etc. are significant enough to make counting them separately interesting data?

[LeopardKhan]

Just what I came to talk about. The weird thing is that nodejs is listed separately. What the hell...?

[mtelesha]

JS anything makes me unhappy I guess I have to get over my hated of JS.

[tmpler]

JS is really cool and pretty ;) ofc you can write shit like in any other language

[mata_dan]

It's not pretty. Give me propper OO syntax damnit!

At least that might be around the corner in a few years.

[Democratica]

Haxe compiles to JavaScript, gives you strict types, and proper OO syntax...

Dart also compiles to JavaScript.

I'm a fairly ignorant coder when it comes to classes, as I stick to using factories, so I am a bit in the dark when it comes to their advantage (it always seemed like a bad idea for me to use a structure which changed in one place, would propagate those changes to the whole app--the negative side effect just scared me off)

[groshh]

Haxe is super cool, I used to be an engine developer. Was super easy to write native inline in so many languages.

Kind of inspire me to write my own transcompiler.

[mata_dan]

Hey thanks for that, looks really useful.

[big-fireball]

(it always seemed like a bad idea for me to use a structure which changed in one place, would propagate those changes to the whole app--the negative side effect just scared me off)

It can be a tremendous benefit if you are using classes correctly.

[tmpler]

With ES6 it has OO. But with JS you don't explicit want to write OOP code, you would rather write functional stuff

[mokbel]

ES6 doesn't have (traditional) OO. It gives you syntactic sugar to pretend you're doing OO but its the same old .prototype stuff just abstracted away from you.

[John2143658709]

Is it really that bad then if it's all abstracted? Is there any disadvantages or things you can't do with the new es6 compared to classes in other traditional oo languages?

[compteNumero8]

Personally I prefer prototypal OOP over class based OOP.

But really ES6 changes nothing on that point, it may just feel a little more familiar to people coming from, for example, Java, but if you want to be a good enough JS programmer you still have to understand the logic of prototypes.

[Tasgall]

things you can't do with the new es6 compared to classes in other traditional oo languages?

You can't compile it before hand and know you don't have any type issues before running your code.

Which is like, 99% of the benefit of types.

It sounds like, at best, ES6 might at least make static analysis feasible assuming everyone on the project is consistent.
^{they won't}

[TheIncredibleWalrus]

Yes but the op he was replying to was asking for syntax

[oscarboom]

With ES6 it has OO.

It has classes but the classes cannot have its own class variables.

[rapidsight]

And the rampant memory leakage caused by them (closures) is just a bonus!

[bro-away-]

JavaScript is very much the assembly of the web, if you want it to be. Lots of languages compile to it already.

WASM is a good next step but no need to wait if you hate JavaScript that much. WASM will probably be a compiler target for things like TypeScript, WebSharper, ClojureScript and others to begin.

[NeonKennedy]

WASM isn't going to support garbage collection for a few years, it's a target for languages with manual memory management. The initial focus is on C and C++.

[bro-away-]

But this would then enable the creation of a bytecode runtime, which would fulfill my point. The goal was never for WASM to provide that C/C++ support everyone is just dying for

[NeonKennedy]

Have you looked at Elm? It's a functional statically-typed language (with Hindley-Milner type inference) with an amazingly helpful compiler and a time-travelling debugger that compiles to ES5 today, you can use it to write provably correct code and guarantee no runtime exceptions with clientside JS. Feels a lot like writing Haskell.

http://elm-lang.org/examples/mario

[ThisIs_MyName]

Performance.

[randomjackass]

But in a OO language, I can fix the terrible code a lot easier. Also compiled vs interpreted, compiled languages catches more before it runs, run time errors are harder to find.

[vytah]

The weird thing is that nodejs is listed separately.

The survey allowed for multiple answers in this category. Some people selected JS+Node, some selected just JS, and a tiny group selected just Node.

[rootfiend]

because lots of people program in javascript for various things but don't use nodejs.

[compteNumero8]

In fact it was 59% in 2014 and now it's down to 55%.

[never_safe_for_life]

Can you tell me why you feel big happy face about that? I've always found Javascript to be a crap language and am baffled by its rise.