Converter VS FS2

The longer story is that st-material-ui incorporates https://github.com/ScalablyTyped/Converter/pull/487 in order to get much, much cleaner API. You'll probably have seen the fake literal types, some rewriting from type unions to inheritance, things like that.

Given that you want interoperability with js, I'd start by playing with https://scalablytyped.org/, then, play with the scalajs-react demos (https://github.com/ScalablyTyped/ScalaJsReactDemos) and the slinky demos (https://github.com/ScalablyTyped/SlinkyDemos). There are some libraries that scalablytyped doesn't support pretty well but you can leverage https://github.com/nafg/scalajs-facades for those.

ScalaJS is awesome. Really solid and mature project, can totally recommend.

The only thing that can be annoying is when you want to have a typesafe interface and have to write a lot of adapters for javascript libraries.

Fortunately there is even a project that can make use of typescript interfaces for those libraries, so that you can use them from ScalaJS more or less automatically: https://scalablytyped.org/

I'm using it mostly for full-stack web development with ScalaJS (https://www.scala-js.org) in the frontend (https://outwatch.github.io/docs/readme.html) and in the backend with AWS lambdas.

The ecosystem is currently in the process of porting all the libraries to Scala 3. So if you're new to Scala, I'd recommend to start with Scala 2, which is rock-solid and already very powerful.

I never worked with SQLAlchemy. But on the scala database side, popular libraries are Doobie (https://tpolecat.github.io/doobie) and Quill (https://getquill.io). Keep in mind that these are for Scala on the JVM. On the ScalaJS side I'm using the javascript library pg. But I'd like to try if it works well with Prisma soon.

The nice thing about ScalaJS is, that you can use Javascript libraries. And if there are typescript facades, then you can transpile these to Scala and use them in a type safe way (https://scalablytyped.org).

Recently, CE3 has had similar issues reported across multiple repositories, almost an epidemic of reports!

Thanks for the explanation!

So it's pull based and not push based like most other streams lib.

Does maybe someone know how this compares to FS2 or Iteratees than? (Both are also pull based streaming solutions).

https://fs2.io/#/

https://en.wikipedia.org/wiki/Iteratee

Looks quite similar to me. Is the Scala FS2 lib maybe even a clones of the Haskell solution? Or are they different in important aspects?

Most important/known: * https://http4s.org/ - an HTTP client/server * https://github.com/typelevel/fs2 - streaming * https://github.com/tpolecat/doobie - JDBC

On the contrary, switching to the functional mindset, with something like Typelevel Scala3 and respective cats and cats-effect fs2 frameworks, helps to rethink a lot of designs and development approaches.

fs2 for streaming.

Finally, the last chapter has been rewritten to be based on some of the main design ideas from FS2 (https://fs2.io), which I hope will be more approachable than the 1st edition.

Just to clarify, is your doubt about the meaning of the api, or do you think you have found a bug? In either case, you can also open a Github discussion https://github.com/typelevel/fs2/discussions.

Another more reactive solution would to use signals, as in FPR sinal network. fs2 implements this very nicely here https://github.com/typelevel/fs2/blob/8b285a6b54c63d43ed6aa3bb91365652035c90e5/core/shared/src/main/scala/fs2/concurrent/Signal.scala

Assuming the bug mentioned here is https://github.com/typelevel/fs2/issues/2568, we came up with a partial fix in a day (https://github.com/typelevel/fs2/pull/2569) and a complete fix in 2 days: https://github.com/typelevel/fs2/pull/2572. Note the original bug was opened on a Saturday. :)