Live data from Hacker News

Scala.js no longer experimental

scala-lang.org

1–10 of 135 posts

Re: Scala.js no longer experimental

#4
That's exciting. I have worked extensively with Scala during my Master's project. What I'd really like to know is what this means in the context of the current trend of JavaScript (both client and server-side).

I'm currently working exclusively on MeteorJS, Node.JS and Angular and fail to see the relevance other than porting Scala applications to the web and making Web App development easier for developers familiar with Scala. However, without the kind of structure and inherent capabilities that a MeteorJS or DerbyJS offers, what's the USP here?

Re: Scala.js no longer experimental

#6

That's exciting. I have worked extensively with Scala during my Master's project. What I'd really like to know is what this means in the context of the current trend of JavaScript (both client and server-side). I'm currently working exclusively on MeteorJS, Node.JS and Angular and fail to see the relevance other than porting Scala applications to the web and making Web App development easier for developers familiar w…

You can still use all of your favourite JS libraries in Scala similarly to how one can can use Java libraries on JVM.

http://www.scala-js.org/doc/calling-javascript.html

Re: Scala.js no longer experimental

#7

Or, said another way, Scala now officially runs on both the JVM and in the browser.

Yea. However, wouldn't you think that the current trend in JavaScript makes this a confusing endeavour in terms of what the end result really is?

Nope. The current trend in JavaScript has nothing to do with a type system.

Here, you have one industrial-strength statically typed language that you can write both the front-end and the back-end in. The end goal is to simplify the development of complex web apps, the thesis statement is that static types could make this end goal easier to reach.

Re: Scala.js no longer experimental

#8

Earlier quoted context omitted.

Yea. However, wouldn't you think that the current trend in JavaScript makes this a confusing endeavour in terms of what the end result really is?

Nope. The current trend in JavaScript has nothing to do with a type system. Here, you have one industrial-strength statically typed language that you can write both the front-end and the back-end in. The end goal is to simplify the development of complex web apps, the thesis statement is that static types could make this end goal easier to reach.

I personally hope that within some time this could be adopted on the large scale, I really feel the need for a statically typed language for the front end. However, the biggest obstacle I can see is the learning curve.

Re: Scala.js no longer experimental

#9
More and more languages have that now (F#, Ceylon, Haxe,...), I wonder how well it works in practice, especially in terms of:

- libraries availability

- code size and speed

- debugging capabilities

- ...and interoperability with JS (I recall that F# uses TypeScript definition files, that's a nice approach)

Anyone has more experience with it?

Post reply on HN