Dev survey 2018
WEW LAD, maximum confirmation of Holla Forums theories.
Inclusion is so important u guise. Please change everything about yourself to accommodate these tiny minorities
JS IS BEST IN LIFE
RUST IS LOVE, RUST IS LIFE
FUCK VB. ALSO FUCK EVERY PROGRAMMING LANGUAGE THAT REQUIRES IQ>100
totally worth paying 300K/year for diversity officers right, thats totes what nearly all your employees care about
Grills less POZ than transfaggorts? Still POZ tho
Really weird dataset.
people actually like coding javashit
i seriously doubt that these are even real numbers and haven't been tweaked to push their narrative. stackoverflow isn't exactly unbiased.
What Languages Are Associated with the Highest Salaries Worldwide?
I told you spergs to learn Erlang.
Wait until you recognize that these numbers state people in IT don't care about equality programms.
programming confirmed to be a brainlet job
There are 2 kinds of programmers: those that can do it and those that ride the coattails of the first set.
Always the most valuable information on a site dedicated to people who don't know stuff.
I fail to see how networking library is going to replace Erlang.
Erlang is a programming language and runtime system for building massively scalable soft real-time systems with requirements on high availability. Erlang is only language that achieved 99.9999999% (nine nines) availability in production.
Only thing that is good about Rust is it's static analysis.
Stack Overflow is awesome when you have to deal with languages that have terrible documentation.
Stack Overflow is awesome when you have
Copy pasted code from one of your developer and didn't mind to test it.
This shit happens to me so much that I'd wish the internet never existed.
trusting numbers from these pajeets
Stack Overflow is awesome
cucks & pajeets
What is "South asian"?
Pajeets? Or is it more around Philippines?
it means "asian mexicans"
it's not really binary
for example I'm one of those who can do some of it
it's not the only way to use SO
Erlang is only language that achieved 99.9999999% (nine nines) availability in production.
this is possible to achieve in any language, it's just made easier in Erlang.
the networking library is not really relevant, when you need those 9s, you want hot code reload and distribution, and while Erlang is designed for that, it won't do it automagically, the system needs to have proper design. and if you got it, it's certainly doable in some other languages too.
but the biggest surprise is that very few projects actually need those 9s.
if it was actually asked like this, it's impossible to know now, because every participant could interpret this as they wish.
you want hot code reload and distribution
In addition to those, one thing that makes Erlang really resilient is supervision trees.
In fact they are so good at handling errors that best practices of Erlang programming tell you to 'let it crash' instead of trying to handle all the edge cases. Basic idea is that it is better to restart from the clean state than to try to reason about all the things that you need to do to recover from every possible error condition.
It works like this, you have tree of processes/actors and if process crashes you restart it, if it crashes too many times during some period of time you restart it's parent process (and whole subtree under it) and if that parent process is restarted too many times during some period of time then you restart it's parent and so on. If root node crashes then whole program crashes. Programmer is one who chooses acceptable number of crashes and over which period are allowed for his code. I have not seen any non-BEAM (Erlang Virtual Machine) language that has anything like supervision trees.
Another thing that makes Erlang safe is share nothing concurrency, but it is double edged sword. It prevents all errors that data races cause, but it copies data a lot.
Last thing that makes Erlang so safe is that messages sent to process are processed serially, on first come first served basis, one at the time. This makes it really easy to write actors because you do not have to worry about all the pitfalls of parallel execution.
Those things make Erlang 'write once, run forever' programming language.
tl:dr; Erlang focuses on safety more than anything else, so you get program that virtually never crashes but does not perform well at calculating stuff.
easy to implement in almost any reasonable language
and yes I know how it works. I worked on an Erlang codebase as well.
it's all good, but again it won't do magical shit if some important code path crashes 100% of the time because the error condition doesn't go away.
it's probably nice to be able to ignore errors which happen rarely, heisenbugs in particular. but you still have to get rid of most programming errors.
even without supervision trees, it's trivial to restart a service if it died. no code is even needed for this, your init system of choice can deal with it. (yeah even systemd) and if you're not doing stupid shit at start-up, this can even be fast.
re. actors and messages, again, it's not a fucking magic, you can overflow the mailboxes for example or shoot in the foot in a different way.
and again, share-nothing model is easily done in most languages if you need it.
sage for dbl post