Indeed. My thoughts and prayers go out to the gunman and his family for not being a better shot

How come sex robots and brain jacks are never an option?

Its the same with a 'good idea'... poison the purveyors. Make the people pushing the idea or supporting it look incompetent, then portray them as reprehensible. Then show how the idea is pushed by those who are reprehensible and you have tied the idea to reprehensible people hance the idea becomes reprehensible through association.

Its a series about a child with a dream who funds himself in his cave with the help of his butler. He builds forensic devices and military grade weaponry and does his own field testing. Wonderful series.

For all the BS about Groovy not being functional, if you look at partial implementations, Groovy is just as functional as Scala. And better yet... it is 100% compatibale with Java; Take ANY Java class and change the extension to '.groovy' and it will compile!

And in other news... 'Water is WET'. Film at 11.

Dynamically typing is VERY handy. I can code very quickly in a development environment and then once stable, make sure what I want to move to production is statically typed. It makes your development more agile as a result. Thus you get fast development speed and high scalability. Doing everything statically (and I dont care how good of a programmer you are) takes a LONG time to code, debug and compile.

Kotlin is a nice language as is Groovy; they both provide similar functionality in different ways and compatibility with Java. Scala does NOT provide compatibility with Java. One advantage is that Groovy is much further along and much more widely adopted; it is part of the Android Development toolkit after all.

Actually Groovy is far simpler and integrates with Spring and is 100% compatible with Java. In fact if you take any Java class and change the extension from '.java' to '.groovy' it compiles 100% of the time.

Well to correct your Groovy statement... all Java code can convert to Groovy with 100% compatibility; change any Java class extension from '.java' to '.groovy' and it compiles 100% of the time. That because Groovy is just a layer of convenience code on top of Java. Scala attempts to REWRITE Java and thus causes an incompatibility with Java and Java libraries.

With all the Scala hype, people neglect to point out that Scala is NOT compatible with Java; alot of libraries and tools have to be rewritten to work with Scala. This is why LinkedIn dumped Scala, Spring dumped its Scala adaptation and more and more companies are dumping Scala. And for all its hype on 'functional programming', you can do the EXACT same thing in Java and Groovy with 100% compatibility. In fact, every Java class converts 100% to Groovy; take any Java class and change the '.java' extension to '.groovy' and it will compile without issue. The same CANNOT BE SAID OF SCALA! This is because it is not compatible with Java and requires Java rewrites in order to be compatible.

Incorrect. Message queues dont share IO state either. You would know that if you tried to pass back to proxy or api server. They cannot synchronize state and the best people have figured out is to pass a 'state token'. This doesn't work however because IO's central version of truth is where I/O meets and so when proxy sends state token, api server may have different state because they didn't synchronize since last update to api server. Or perhaps MQ has different stae from api server and thus rejects because it didn't synchronize. Yeah so... nothing like MQ my friend. Try to understand I/O before commenting like a monkey behind a typewriter

Showed this to Netflix once and they stated 'This fixes everything we are currently having issues with'. Apparently the entire industry has implemented API's in distributed architectures in such a way as to create architectural cross cutting concerns... https://www.slideshare.net/bob...

KEXP... nuff' said.

I HACKZORZ ur APPS W1T my luddite shell