why I like scala.js

why I like scala.js

scala.js is a scala compiler that compiles scala to javascript. There are many languages out there that compile to javascript.

So why do I like scala.js? You’ll see that my argument could probably be made for other transpilation-capable languages as well.

In no particular order:

  • I already know scala so this allows me to re-use my skills.
  • I was tired of JVM issue and uncertainties about its future. Although Oracle now seems to be investing in the JVM ecosystem, I am wary of historical trends. Also, the JVM is not critical in some types of program architectures. The other aspect is that scala has remnants of the JVM built into it. Life is tough, but I found that JS handles some things differently that I liked better, such as not forcing errors into a specific type (JVM only allows errors to be Throwables).
  • Built on javascript, scala.js interop with javascript allows me to remove a large category of thorny issues that nearly all JVM languages have–how to adapt language constructs and semantics to general purpose data structures used in a wide variety of libraries that improve my productivity . This is actually a really big deal for me. Since one class of application that I care about are web front ends (as well as backends since I am a data scientist), the use of javascript with scala.js interop allows me to translate scala level constructs into a common data format that is easy to work with. JSON is everywhere in javascript. And like with Lisp, where lists and dictionaries were flexibly and builtin as foundational data structures that all lisp libraries used with great flexibility, you can turn scala level data constructs into JSON easily. This allows you to avoid using/building complex serialization/deserialization libraries as well as avoid some aspects of data management libraries. For example, creating diffs of objects or breaking an object into dictionary and back again in a typesafe way sometimes requires complex introspection or compiler macros–in javascript most people could write their own or some variant that is good enough to get work done.
  • scala.js works well.

We all have opinions about javacript and JSON–that’s Ok.

From my perspective, javascript/JSON is good enough on both the server and a javascript agent like a web browser to make programming easier and less complex for certain types of applications-not all. Using scala.js allows me to obtain benefits of scala semantics and ecosystem while still using the interop to javascript/JSON to take advantage of the strengths in the javascript/JSON of the ecosystem. I do not need extra macros, complex libraries or other things that are necessary when using a JVM language when performing some data operations.

I do not need everything perfect and programming will never be perfect. The incremental benefits of using scala.js are good enough for me to improve my productivity and ability to deliver better client solutions faster.

That’s it!

PS Yes, I keep track of other languages that also have javascript capabilities like ReasonML (OCaml), dart, clojure, typescript, Haskell (kind-of). In strategy terms, scala.js allows me to stay in the scala ecosystem whereas I would have to leave scala to do something that requires javascript. Once you leave the ecosystem, even for part of the work, you are at risk for churning a programmer to another language and ecosystem in their entirety.

Comments

Post a Comment

Popular posts from this blog

quick note on scala.js, react hooks, monix, auth

quick note on scala.js, react hooks, monix, auth Reactjs hooks finally came out of preview in a recent version of React. scalajs-reaction has had support for hooks since they were in preview. React hooks seem like the hot new thing but for me the question is, do hooks help improve your code by improving maintainability, time to market, TCO, etc.? Let’s take a look using authentication as an example and employ monix , a reactive observable framework that also builds on cats . We will assume we are building a SPA. Does it improve your code and make your application & development experience better? Auth Auth processing can be complex. Many react auth examples you find in blogs like to show how to use “react-routing” and “auth” as a switch that determines which routes are protected or unprotected. Protected routes show application specific data. Unprotected routes show login content . Based on storing a “User” object in the browser session/local storage, th...
Read more

zio environment and modules pattern: zio, scala.js, react, query management

zio environment and modules pattern: zio, scala.js, react, query management This blog covers a zio-based fetch design for scala.js, react web applications. It heavily uses the zio “environment” feature to help motivate a point of view on the modules pattern in effect systems. At the end, I summarize some thoughts on ergonomics and complexity. This blog assumes a basic knowledge of zio and react. scala.js is just like scala so you mostly already know scala.js. This blog is a follow-on to previous blogs: https://appddeevvmeanderings.blogspot.com/2019/10/scalajs-react-fetcher-hook_48.html and https://appddeevvmeanderings.blogspot.com/2019/11/scalajs-and-react-suspense.html . I have been keeping an eye on and culling ideas from typscript/javascript fetching libraries that address query management concerns. The formulation below incorporates some of those concerns but does not try to comprehensively duplicate well established javascript libraries. I only care about ...
Read more

attributes with react and typescript.md

If you use typescript with react you may wonder what the right signature is for your “properties” interface. Obviously, your component will have few to many specific properties that reflect your domain. However, you may wish to also provide for the ability to add other attributes, such as those valid for a div property. In other words, you want to extend your props interface with that of the properties from a div element. How do you do that? There are really two issues: How do you extend your props interfaces How do you filter the props once you receive them to just those that apply. Extend Your Prop Interface or Use Sum Types It’s not uncommon to see interface Props { className ? : string yourProp ? : number } with the idea of using it in class MyComponent extends React.Component<Props, any> somewhere. If your component will have an outer div, you may also pass in a react element so that its configurable. But let’s say your outer element is a div and you wan...
Read more