typescipt, clojurescript, flow, scalajs, haskell and other type-oriented javascript transpilers

It is well known that it can be difficult to develop javascript applications due to the lack of a static typechecking transpilation stage. While it is a strength that javascript is typeless, many types of programming tasks and applications greatly benefits from typechecking. There are good reasons to completely ignore static type checking, such as in most javascript programs or clojurescript programs. However, even common lisp has static (and dynamic) type checking (it's not well known that the compiler can type check).

Typescript, adopted and promoted by the google angular team, has become very popular especially in the past few months. Its been organically growing for many years and its a good example of Microsoft contributing to the open source community. Typescript is a light layer on top of javascript that allows you to typecheck your programs. Perhaps some of the features in typescript will be moved into the javascript standard, perhaps not. Flow, facebook's typechecker, is similar.

The issue with all statically typed languages written on javascript is not so much the application you are developing, but the bindings to the large, and growing larger, ecosystem of javascript libraries.

Typescript has an entire site dedicated to typescript modules for common libraries (github typescript umbrella project). The same issue applies to scalajs, a scala implementation running on javascript. A recent project provides comprehensive bindings for the standard nodejs library: (github scalajs nodejs comprehensive bindings). scalajs has a compiler that translates typescript bindings to scalajs bindings and is a great starter (github typescript to scalajs bindings converter). "Definitely scala" has used it to auto generate many scalajs bindings similar to the collection of typescript bindings (here).

These bindings are really the difficult part of using a typechecked javascript. scalajs has a nice bundlor that uses webpack and npm to grab any npm library you need. It's easy! But, you have to find those bindings. Over time, this should be less of an issue, but the bindings do have to be updated as a library's javascript API evolves---and tracking changes is not a strong suit for many open source projects. It does make me wish for some features in common lisp where you could incrementally add type information to your programs.

I tend to think that the bindings are key parts of driving adoption. That's why the scalajs nodejs bindings could be a game changer as nodejs becomes, arguably, the third major platform architecture like the JVM and .NET.


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

user experience, scala.js, cats-effect, IO

user experience, scala.js, cats-effect, IO This is not a complicated snippet but I wanted to ensure I remembered it. When creating a UI, say react for browsers, you will run into the “fetch” data problem. When you fetch data, you typically have a component that performs the fetch and acts as a cache for the result. The fetch component renders a child and passes along the data that was fetched (or the fetch state, etc.). Even with the upcoming react suspense mechanism that will make this a smoother user experience, you may have a flash of a “loading” indicator that shows for a moment before the content is fetched from the server. If the flash is too fast, it is visually disruptive. A shimmer mechanism for the UI my also not be the answer. Similarly, if the fetch request takes too long, you will want it to time-out and show an error message that the data could not be fetched or whatever is appropriate for feedback in your application. Generally, I use cats-effect
Read more