dotty scala3 adoption report: easy so far

dotty scala3 adoption report: easy so far

I decided to use dotty (aka Scala 3) for a small machine learning (NLU) project to get a feel for new features and ecosystem components. I try to keep my code simple to write and understand. I tend to avoid the use of advanced type features, and I am Ok if I avoid “purist” FP thinking. I don’t mind a little boilerplate.

Here’s some feedback. More to come when the project is complete:

  • Adoption: Easy. I read some dotty slides for an hour. Then I read the dotty doc site for another hour. So far, the dotty features I have chosen have been easy to adopt, e.g., implicits with the new syntax via given. Dotty is an experimental compiler, and I found a bug! The dotty team fixed it within a few days–thanks!
  • New features: I am using a few, new features including:
    • implicit functions (they immediately added value)
    • objectless toplevel code
    • extension methods
    • ADTs via enums
    • union/intersection types
    • exports
    • The features were easy to learn, adopt, and I quickly became used to them. I had a few assists from the gitter dotty channel about a few complex features but I dropped their use until they are better documented and fully implemented.
  • sbt support: You can use scala2 (less macros) by using a sbt syntax extension on your scala2 dependencies in build.sbt. This approach has worked for cats, circe, zio and a few other libraries I needed.
  • Roadmap: The team seems to have listened to the community about migration support, backward compatibility, and editor support out of the box. These topics are discussed in multiple venues. The Roadmap schedule appears to provide a generous on-ramp period, and there is consistent communication about features, development process, and the schedule.
  • graal (not dotty related): I have sbt running on graal, and I use graal as much as possible. I do not know if it is graal or sbt updates or both, but compilation (delta and full) is fast. graal also gives me a path, along with scala-native, towards mobile devices running ios and android. Oracle is heavily investing in graal. Allowing graal to do the heavy-lifting for mobile is a smart move and probably was part of an unspoken plan to have scala be relevant on mobile devices. As a side note, graal renewed my faith in JVM-based languages.

I like dotty’s new syntax and features. It was straightforward to pick up. Perhaps for code that uses simpler scala 2.x features, the conversion may be relatively easy although not cost-free. Hopefully, runtime performance will be excellent once GA.

My experiences may not overlap with those that have large complex code bases to build and maintain. My initial reaction is that the transition to scala 3 may have some bumps along the way, but it does not appear to be earth-shattering or overly difficult. The scala teams seem to be taking reasonable steps to make it easy.

At this point, I think that scala 3 success is related to the execution of the plan vs. a lack of strategy.

After adopting dotty, I was back to the same challenge I always have: how to represent my data and functions in a way that compose and are fast to run. I have some new tools in the toolbox to help me.

Note: The project depends on zio, xtract, circe and cats.

Comments

Post a Comment

Popular posts from this blog

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

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

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