[easel]

I'm in the process of introducing Scala.js to the front-end of seventh sense. My navigation and several display components are in production already, with more coming all the time. Once you understand the interop rules and get a unified toolchain in place, it "just works", and as others have said, having access to scala typing and the same, typed, codebase on both front-end and back-end is awesome.

I'm currently using Angular, React and Moment.js on the scala side, so I can confirm JS library interop is possible.

[_lbaq]

How would you describe the level of effort needed to deal with the interop ? "Is possible" can range from "Its possible" to "Very nice" :)

[easel]

I'd say the language level interop is "very nice". Library level interop is still a work in progress. Many (most?) facades are incomplete, and the more complete ones often eschew compatibility with existing JS code in favor of optimizing for scala-js only. Typically figuring out exactly what the possible argument and return values are for a given js function takes a bit of trial and error, so you have to twiddle the facade a bit and be prepared to fork them and contribute changes back upstream.

That said, if you're familiar enough with both platforms to handle an app that has both, moving the interop from your head to the scala.js code isn't that big of a leap.

[_lbaq]

Thanks, I have to dig in and see how much of an issue missing library integration in my case would cause.