Let's rank programming languages by good vs evil and lawful vs chaotic! Here's my ranking:

Let's rank programming languages by good vs evil and lawful vs chaotic! Here's my ranking:

Lawful evil: Java
Neutral evil: C++
Chaotic evil: Javascript

Lawful Neutral: ADA
True Neutral: Python
Chaotic Neutral: C

Lawful good: Haskell
Neutral good: Lisp
Chaotic good: Perl

Other urls found in this thread:

labs.ig.com/static-typing-promise
twitter.com/NSFWRedditVideo

Still reconsidering the Chaotic good and Neutral evil choices though.

>ADA
i am pretty sure the american disabilities act is not a P.R.O.G.R.A.M.M.I.N.G. L.A.N.G.U.A.G.E.

Now I know why I like C so much...my life goal is to be like Perl or Haskell

Those evil choices are also alarmingly accurate (Java and C++ in particular)

>no node
DROPPED

Lawful evil: Python
Neutral evil: Common Lisp
Chaotic evil: PHP

Lawful Neutral: Java
True Neutral: JavaScript
Chaotic Neutral: C

Lawful good: Clojure
Neutral good: Ruby
Chaotic good: Perl

>neutral good
>Ruby
>good
DROPPED

(I believe the evil rankings though)

It's primary goal is literally to make developers happy, and has one of the lowest bug densities of any language.

If that's not good, I don't know what is.

anything on the good side is pretty subjective, but the evil is on point

This thread is so fucking stupid. How the fuck do you rank programming languages on those completely unrelated axis?

Fuck off, OP.

Subjectively!

There isn't much point, besides it's kinda fun to do.

kys

To be fair, I may have been traumatized by rails at uni. I'll have to evaluate ruby again sometime. Still don't like the gems thing though, and the way colons are used...

Oh, old Rails is a horrible place to start with it.

I think it's best to play around in a REPL like Pry to get a better idea about the language in general. It allows you to navigate your namespace like a filesystem. (So you can "cd" into variables, "ls" to see members, run functions like commands, and pull documentation)

Also, if you put "binding.pry" somewhere in your code after requiring pry, you can use it like a debugger, or to run any code from any context ever. You can basically put it at the end of an incomplete function to experiment and build a bridge as you are crossing it, Lisp-style.

Also, method chaining on collections is the shit.

...

BEST: javascript es6.

OP, your image was incorrect. I fixed that for you.

Not user, but I see what you did there. Cheeky...

top kek

Filename was sort of a giveaway.

...

>(((((((((good

It is though.

that study was all kinds of flawed. You're making a fool of yourself by using that graph

Slightly flawed perhaps, but still reasonable and it shows an interesting correlation: labs.ig.com/static-typing-promise

>((((((Common Lisp)))))))
>((((((((((((((good)))))))))))))))))