Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Only If You Plan For Your Code 2 B Incompatible (Score 1) 245

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.

Comment Re:Kotlin (Score 1) 245

...groovy is still stuck with the "mistakes" of java as well which is what Scala attempts to fix with the rewrite. Kotlin is also a rewrite but does a great job of "fixing" java without causing the compatibility issues that Scala creates.

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.

Comment Re:Kotlin (Score 1) 245

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.

Comment Only If You Plan For Your Code 2 B Incompatible (Score 3, Informative) 245

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.

Comment Re:As if to echo your point (Score 1) 266

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

Comment As if to echo your point (Score 0) 266

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...

Comment Improve The Economy (Score 1) 477

Employed developers make happy developers... and ones with far less time on their hands. Thus they dont spend their time on forums all day. Improve the highly exploited H1B program, make laws that protect employees for unlawful firing practices, etc etc. BUT... since this will NEVER happen, expect those comments to continue. Sorry.

Slashdot Top Deals

Logic doesn't apply to the real world. -- Marvin Minsky

Working...