Does this provide a garbage collector?
Boom GC is a dependency
Scala Native v0.1
41–50 of 254 posts
Re: Scala Native v0.1
#42Does this provide a garbage collector?
[deleted]
Re: Scala Native v0.1
#43It seems to me like Scala's biggest benefit and biggest downside are two sides of the same coin: easy interop with the JVM and Java code. Scala Native just seems like you're paying all the price of that for none of the benefit.
Well, this is just targeting a different VM, LLVM instead of the JVM. You get easy interop with all LLVM languages with this, including C.
Easy interop with C++ or Rust? I'll believe it when I see it.
Re: Scala Native v0.1
#44Earlier quoted context omitted.
Well, this is just targeting a different VM, LLVM instead of the JVM. You get easy interop with all LLVM languages with this, including C.
Easy interop with C++ or Rust? I'll believe it when I see it.
It looks like it can!
http://www.scala-native.org/en/latest/user/interop.html
>Scala Native provides an interop layer that makes it easy to interact with foreign native code. This includes C and other languages that can expose APIs via C ABI (e.g. C++, D, Rust etc.)
Re: Scala Native v0.1
#45It seems to me like Scala's biggest benefit and biggest downside are two sides of the same coin: easy interop with the JVM and Java code. Scala Native just seems like you're paying all the price of that for none of the benefit.
I started working for a company that does a lot of Scala a few months ago. It's my first real exposure to it.
To me, Scala's biggest benefits are just the language itself. So many little things that I couldn't do in Java, I can do with little effort in Scala. I can write imperative code if I really want, but I have all the benefits of functional programming available too.
Re: Scala Native v0.1
#46Will macros work with Scala Native, as they do with ScalaJs? (I believe that compile-time metaprogramming is the way forward, especially if the target doesn't support reflection or dynamic code loading).
Re: Scala Native v0.1
#47Earlier quoted context omitted.
Long time Java lover here. I agree with all your points, but in the context of Java at least (does Scala support this?) there is no simple static binary that can be built and released, which includes the JVM. I think 1.9 will have this option, but this is something I didn't realize I missed until I started work with Rust and Go. It makes deployment so much simpler.
In the age of containers it's really not that much harder to build and deploy a JVM app. Edit: thanks for the downvotes but you could at least tell me what's so crazy about my statement.
One app, sure.
At work I'm running 17 different containers- many of which require their own JVM. (That's 3 different JRuby apps, zookeeper, kafka, and ElasticSearch.)
Those JVMs get heavy when you're shipping container images compared to small Go or Rust binaries.
Re: Scala Native v0.1
#48It seems to me like Scala's biggest benefit and biggest downside are two sides of the same coin: easy interop with the JVM and Java code. Scala Native just seems like you're paying all the price of that for none of the benefit.
Well, this is just targeting a different VM, LLVM instead of the JVM. You get easy interop with all LLVM languages with this, including C.
LLVM is not a VM in the same sense as the JVM is.
Re: Scala Native v0.1
#49Does this provide a garbage collector?
Yeah it uses the Boehm garbage collector.
Re: Scala Native v0.1
#50As a Scala guy on a Scala team, I'd think this would be most immediately useful on smaller fill-the-gaps sub-projects where we have to integrate with native code.