@alvinalexander Try/Either is more convenient for handling errors (e.g. propagating with 'map'). With the union types, you'd need to always pattern match, right?
hey @mhevery . I'm wondering what are expected numbers of js files by default without any manual 'bundling' in #qwik ? E.g. for a big enterprise webapp (tens to hundreds of 'screens').
Contemplating if @scala_lang could have 'for comprehensions' without the for blocks. Similar to @roc_lang backpassing. All you need is <- comprehension.
Having background in Java, Scala, Typescript and a bit of experience in Elm and Rust I find the #roc language the most promising new generation FP language. I'm sold to all of the design choices. @rtfeldman does a tremendous job!
@jdegoes Doesn't F[_] wins all Typelevel users and 'a few' ZIO users. The few depending on maturity of the library? As an example to use http4s and ZIO since it's easy to integrate (because of F[_]) ?
So what's the alternative to #akka if I need to spawn thousands of stateful concurrently accesed 'objects' with various lifecycle requirements. It should scale beyond single machine.
@adamwarski@zioscala Great post. I concur that service vs business logic semantics and respective DI is a bit confusing. I guess this will get better with experience on larger codebases.
Most devs know standard falsy values in #Javascript. But there is document.all API. Returning HTMLAllCollection which is Array like and still falsy value! Despite having non zero length and being iterable.