Re:AWS Java documentation is fucked
by lostcolony on Saturday February 13, 2016 @12:21AM
(#11092678)
And then you find out pjlegato switched to Elixir, where he gets lightweight libraries by default, real threading, no GILs, no callback hell, uses all the cores trivially, in a single process, -and- gets a concurrency model that doesn't suck, baked in distribution that doesn't suck, better VM introspection, fault tolerance second to none, tail call optimization, soft real time performance, higher order functions, and glorious, glorious pattern matching.
Or maybe not, but just sayin', you're making assumptions in trying to defend Java there. It's enough to say "You don't have to write Java that way", and then find reasons why Java stands on its own ("It's the lingua franca of software development", and related, is the best I can come up with, but eh), rather than attacking a strawman by assuming what traits the language(s) he switched to are and comparing Java against those.
I think pjlegato switched to Clojure, where you get pretty much everything you mentioned there too. At least looking at his github commits.
Re:AWS Java documentation is fucked
by lostcolony on Sunday February 14, 2016 @11:39AM
(#11098899)
There ya go then. Though, Clojure doesn't have most of those additional things I listed either, as most of them are requirements of the VM rather than the language (it does, however, have a slew of other things that make it awesome, and it has the language level features I mentioned)
Yep, this. I <3 Clojure!
Lein is one of the simplest and sanest build tools I've ever used.
I thought the same until I actually tried working on big projects with other, simpler languages. Threading can be replaced with process forking in those GIL languages, and everyting else is just so much better. 4 years after ditching java I will never ever want to write code in it again.
The world has a few other languages besides Java, Python and Ruby. Not every language has a GIL, and its the damn 2010s and we've got other concurrency models worth trying beside the 90's staple of mutex-littered multithreaded apps or callback hell.
And, as a bonus, with Java you get real threading, don't spend all day working around single threaded interpreter GILs or dealing with call back hell. You can actually use all the cores on those CPUs, in a single process if you want!