As someone who has dropped Scala on the backend (not doing FUD, just not happy with the JVM memory reqs)- what keeps me still using scala is Scala.js.
While some argue that there is more readable code with Bloomberg's OCaml.js, I like Scala.js because of Scala itself, which is
1) Very well designed
2) Lots of "functional" constructs in accompanying libraries
3) Good typechecking
4) Fun language to use.
and because Scala.js interop with JS is very seamless.
Do check out ScalablyTyped repo on Github, a Scala.js analogue of DefinitelyTyped.
Being typed- one of the best things I like about Scala is that I can do something like this (provided by a couple of frameworks- Laminar, Scalatags et al)
No more mismatching tags, wrongly spelled tags, unclosed tags. Typechecked HTML in some sense.
This would also be a good place to mention some alternatives where a mainstream language can also compile to JS so hopefully people can comment with their experience:
1) PureScript
2) ELM
3) Clojure script (child comment)
... and of course... TypeScript! :)
It should be noted that while Scala.js isn't as popular as some of it's alternatives in "popular" programmer culture, the author is very focussed on correctness and I don't know of anybody who has ever used Scala.js for a project but dropped it. (Happy to be corrected)
I'm curious if you did any measurements and what you prefer instead.
The managed heap is very efficient. I have a web server (built in Scala) configured on my own VPS to run with a 10-100 MB heap. To this you add the JVM's memory used for managing OS threads, opened sockets, JNI, GC overhead and I end up with a process using 190 MB (RES), which is reasonable for a server-side process, because you can actually do a lot in it, Java processes being able to be fat.
In my experience a well grown Java process will be much more efficient and predictable in terms of memory used than Node.js, PHP, Ruby, Python, at the very least.
The only problem I've experienced is the startup time, plus depending on use case I might prefer native binaries. GraalVM looks promising.
Scala.js is useful on the sever for example if you need to work with "serverless" tech, e.g. AWS Lambda, for which startup time is important.
I have some very simple lua processes that consume 2MB. They basically do nothing but listen to a websocket and run some shell comands. Lets say I have 3 of those. With the JVM I would have blown away more than half a gigabyte. Even with micronaut you're looking at 100MB per process. This just isn't sustainable. I personally think the JVM is a piece of crap because of this.
There is GraalVM but compilation takes a relatively long time even compared to a C++ project and as soon as you use features that it doesn't support it will fail to work which means you are stuck with Java because you don't want to risk using a language that doesn't officially support GraalVM (groovy kotlin etc).
True, but in the same way that a 747 is terrible for delivering pizza.
You may be right that Java doesn't scale down well, but that's not normally the sort of work it's intended for. (Let's ignore the applets mistake.) It's a terrible solution for scripting, yes, but for heavyweight server roles I'd be surprised to see it significantly outperformed by .Net, and there's really no way Lua or Python would be able to compete.
OpenJDK has a very impressive (and heavyweight) JIT, for instance, and very impressive GCs of almost no use for short-lived applications.
With all that said, it'd be great if OpenJDK's new developments mature to the point that Java can become practical for 'lightweight work'.
well compared to dotnet core 3 the java memory management is really really bad.
in java memory is not more efficient than in node.js/php/ruby or python it's worse. what is better is the performance, especially when you have a lot of stuff on the heap the performance is predictable even with a memory size of > 16gb where the other languages lack of. GraalVM still misses a lot of stuff and is slower.
so I think the biggest buck for the bang actual is dotnet (maybe go is as good as well, but does not really play in the same league). I think once valhalla hits the tables might change, but even than ReadOnlySpan<T> is way too awesume than just value types.
Speaking of the mainstream scripting languages ...
Python often leaks memory, the GC being built on top of reference counting to solve cycles, isn't compacting and can also be left disabled for performance, which is a trap. This is made worse by native libraries that also leak. It has gotten better, Python apps being one of the most deployed. But I haven't seen a Python app that's memory efficient yet, except for short lived shell scripts.
PHP uses tens of MB per request, which due to its "shared nothing" policy means you need several GBs of RAM for serving a Wordpress website that can withstand traffic spikes.
Many companies actually deploy their Ruby apps on top of the JVM, via JRuby, due to better memory usage.
Node.js is the only one that's more efficient out of this bunch, the GCs have similar implementations to the JVM and optimized for devices that are memory constrained, the problem being that Node.js processes are single threaded, so to distribute the load, you end up with multiple processes, plus due to JavaScript you also get more garbage.
> the biggest buck for the bang actual is dotnet
Not in my experience, but granted I haven't tested .NET Core yet.
well he talked about the AOT stuff. which is not on par as dotnet core's aot approach in 3.0, however default graalvm is quite fast (but still memory hungry)
I recently learned that Scala.js doesn't yet support generating TypeScript *.d.ts type definitions. I intend to open a Gitcoin bounty to get this work done.
Have you had any success using Scala.js-generated JavaScript in TypeScript projects?
I'm quite interested in a full stack of create-react-app + TypeScript + graphQL + front end libraries written in Scala + back end services written in Scala.
In general I'd advise against using Scala.js for libraries. The Scala.js runtime is pretty heavy, and Scala's and TypeScript's type systems are different enough that it tends to be difficult to design an API that feels native in both.
Have you considered ScalaJS-React[0] or Outwatch[1] instead?
Are you not happy with JVM in general or not happy with how Scala uses the JVM? Things like Spark were written in Scala so I am curious what didn’t work for you.
Spark uses off heap memory via JNI in order to avoid JVM memory management drawbacks. It hides it behind a heavy abstraction, which makes it plausible to use such solution for data processing pipelines, for the smaller applications not so much.
But for most things that is not that much a problem - I'm not saying that JVM memory model makes Scala unusable, just that Spark is not a great example here.
Scala Native [1] has been really quiet of late (last commit July 29), not sure what's going on. There was a lot of excitement when the project kicked off, hopefully it continues to evolve.
The creator and lead contributor has been finishing up his school but I am not sure of his plans for the future. There is a book coming out on the subject, https://pragprog.com/book/rwscala/modern-systems-programming... and I am hoping it will continue to grow and evolve.
While some argue that there is more readable code with Bloomberg's OCaml.js, I like Scala.js because of Scala itself, which is
1) Very well designed 2) Lots of "functional" constructs in accompanying libraries 3) Good typechecking 4) Fun language to use.
and because Scala.js interop with JS is very seamless.
Do check out ScalablyTyped repo on Github, a Scala.js analogue of DefinitelyTyped.
Being typed- one of the best things I like about Scala is that I can do something like this (provided by a couple of frameworks- Laminar, Scalatags et al)
<pre> div( Seq( div( "div 1" ) ), div( "div 2" ), b( "bold stuff", i( "italic inside bold" ) ) ) </pre>
No more mismatching tags, wrongly spelled tags, unclosed tags. Typechecked HTML in some sense.
This would also be a good place to mention some alternatives where a mainstream language can also compile to JS so hopefully people can comment with their experience:
1) F#- Fable 2) OCaml- Bloomberg's BuckleScript 3) Go- Gopher 4) Haskell- GHCJS
Other non-mainstream but compile-to-JS languages
1) PureScript 2) ELM 3) Clojure script (child comment)
... and of course... TypeScript! :)
It should be noted that while Scala.js isn't as popular as some of it's alternatives in "popular" programmer culture, the author is very focussed on correctness and I don't know of anybody who has ever used Scala.js for a project but dropped it. (Happy to be corrected)