Re:The myth of using Scala as a better Java
by divanvisagie on Thursday March 02, 2017 @03:18AM
(#13772524)
It depends how you define "competitive". If you are trying to collect hipster points then Scala is not going to help you but let's be real. Nobody is writing big systems in either Rust or Swift, these are playgrounds for people at the moment.
Re:The myth of using Scala as a better Java
by bontoJR on Thursday March 02, 2017 @03:20AM
(#13772531)
I am big fan of Swift and Scala... and, to be honest, for Swift there's a long way ahead before a big system can be deployed... tooling and libs are not there, also not considering that the lack of ABI stability makes the source code necessary for any external dependency.
Re:The myth of using Scala as a better Java
by nvarsj on Thursday March 02, 2017 @02:42AM
(#13772337)
> Is Scala still competitive to modern languages like Swift and Rust?
Of course it is... swift is a mobile PL, and Rust is barely used non-academically (and also takes a long time to be productive in).
Scala let's java devs immediately hit the ground running, for better or worse, and it's hugely popular in the real world.
Re:The myth of using Scala as a better Java
by yellowapple on Thursday March 02, 2017 @03:29AM
(#13772563)
I don't think Scala's really comparable to Swift, and it certainly is not to Rust. Use the right tool for the right job.
I experienced several drawback according to library quality and code-safety. There are too many small details that left me with an unpleasant feeling (I would take ScalaNLP/Breeze for example).
But my central issue is the VM/GC dependency. In times of GPU computing, native interface programming becomes a burden. The knowledge of object ownership improves code readability. I feel uncomfortable leaving object lifetime to a background process.