11–20 of 25 posts
The reason for using it was that as I rarely have time to spend on the code, and often months apart (when the next term comes around), I wanted something where the compiler will catch more of my mistakes.
(Generally, I've been using scalajs-react on the client side)
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 usin…
How would you describe the level of effort needed to deal with the interop ? "Is possible" can range from "Its possible" to "Very nice" :)
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.
Earlier quoted context omitted.
How would you describe the level of effort needed to deal with the interop ? "Is possible" can range from "Its possible" to "Very nice" :)
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…
I am using the Scala.js for 1 year for commercial product. The quality is very good. All are very happy. The Scala.js and the React are integrate very nicely. I encourage you to try, you can never go back. You will not disappointing!
We are working on a system that monitors, analyzes and reacts to telemetry sent by industrial machines. Part of this project are very JS/Ajax rich interfaces (plural) that show graphs, telemetry updates and alerts in real-time, interfaces that have to be kept up and running in the same browser window for days without refresh. The problems we've experienced is that the client-side is not front-end work, where the people involved need to have UX skills and stuff like that. Oh no, this is about building a reliable UI that doesn't leak, that doesn't choke on too many updates sent by the server and that can recover after networking issues.
Scala.js is great because we can use Scala-related tooling, which are much, much saner than what you get in Javascript's ecosystem (e.g. IntelliJ IDEA, SBT, dependencies managed in Maven repositories, Google Closure tree-shaking your code by default, etc.), a statically typed programming language that can help prevent accidental errors, which is very important for us because the complexity of the business logic involved is very problematic, plus a very rich standard library. For example we don't have to wait for async/await because we already have it. The libraries you can work with are pretty cool as well. Facebook's React is a popular choice for usage in combination with an FP style and interoperability is great. Plus the ecosystem of Scala.js-specific libraries is very active. As a shameless plug, we've built our own library for dealing with reactive streams, cross-compiled to Scala and Scala.js: https://github.com/monifu/monifu
Here are the slides from my recent presentation at "Scala by the Bay" conference narrating our experience so far (video for the same will be released by the conference organizers soon): http://www.slideshare.net/ramnivas2/full-stack-scala
I am planning to use it in production. We are working on a system that monitors, analyzes and reacts to telemetry sent by industrial machines. Part of this project are very JS/Ajax rich interfaces (plural) that show graphs, telemetry updates and alerts in real-time, interfaces that have to be kept up and running in the same browser window for days without refresh. The problems we've experienced is that the client-sid…
We are building a production app using Scala.js (with React as the underlying framework through https://japgolly.github.io/scalajs-react ). It has been a marvelous and super-productive experience. Here are the slides from my recent presentation at "Scala by the Bay" conference narrating our experience so far (video for the same will be released by the conference organizers soon): http://www.slideshare.net/ramnivas2/f…
We are building a production app using Scala.js (with React as the underlying framework through https://japgolly.github.io/scalajs-react ). It has been a marvelous and super-productive experience. Here are the slides from my recent presentation at "Scala by the Bay" conference narrating our experience so far (video for the same will be released by the conference organizers soon): http://www.slideshare.net/ramnivas2/f…
How do the endresult code size look compared to handcrafted javascript ? 2x , magnitude ?
I am using the Scala.js for 1 year for commercial product. The quality is very good. All are very happy. The Scala.js and the React are integrate very nicely. I encourage you to try, you can never go back. You will not disappointing!
Did you use any other framework beside react ?