I kept my twtr account for a while because brands I occasionally reach out to were still exclusively there. It’s now no longer the case so I put the account down for real :)
"to craft a modern, direct-style I/O stack that seamlessly interfaces with the latest kernel I/O advancements, such as io_uring. This is where Eio comes in."
@deshipu@orsinium So your problem is that, unlike some other programming languages like #Scala where you can have an object with the same name as a #type (and in fact Scala has some extra rules for implicits resolutions for companion objects), #Python types are essentially objects.
I think that is a feature, not a bug, as it allows to have #dependentType
@vascorsd per 2022 'Long-term compatibility plans for Scala 3' [1], #Scala 3 mimics the post-2017 'Forward Faster' Java approach, wherein few times a year there will be a Scala Next release with language features, while keeping the binary compatibility with Scala 3.0; and every 2 years or so a Long-Term Support (LTS) release, which promises to be patched for 3 years, analogous to Java 8, 11, 17, etc
FYI Sébastien Boulet on 'Leveraging sbt remote caching on a big modular monolith'
"In case of a full cache hit, the sbt build takes about 3min 30 seconds.
This duration is still a few minutes because not all sbt tasks are cached. .... On the other hand, [a full cache miss] takes up to 45 minutes. Therefore, a fully cached build is more than 92% efficient.
The series of articles titled “My Scala Story” is pretty cool, worth a read 🥰
Interesting to see how many came to #Scala for mostly the same reasons — having fun with #FP 💪👾
Hey, #Scala 2.12.19 & 2.13.13 are out! #Scala 2.12.19 comes with some extra compatibility for JDKs 21 & 22 and a new -Yrelease flag to complement -release for working with old Java versions. And of course - bugfixes!
Check out the release notes here 👇https://github.com/scala/scala/releases/tag/v2.12.19
#Scala 2.13.13 also brings better compat with new (and old) JDKs, as well as extra tools for step-by-step migration to Scala 3, some new linting options and other improvements.
Check out the release notes here https://github.com/scala/scala/releases/tag/v2.13.13 for details on that and more. 👇
The main #Scala event of the year, Scalar, is coming up in three weeks!
Get your ticket for both or either:
🎓#fs2 & #zio trainings on 20th of March,
⚖️conference on 21-22nd of March
During the conference:
🎙️25 awesome talks on FP, Scala, use-cases, data science, Native, JS & more
🎉celebrating 20 years of Scala at the community party
🌃All of that in the beautiful, affordable & easy-to-reach city of #Warsaw! (stay for the weekend, if you can)
"a fairly unique place in the new, vibrant OCaml 5 ecosystem ... I'll compare it to generalist schedulers like Miou or Eio, to process-based parallelism libraries like Parany, and to domain parallelism libraries like Domainslib."
More advancements and research things being done in #ocaml world for futures, fibres, threads, pools, effects, etc.
Soon they will reach the power of #scala effect systems 🫣😌
as part of sbt 2.x umbrella of effort, I am rebooting the sbt documentation into a shape that I would've wanted to read, getting inspirations from other docs, like Cargo. some of the materials would be from sbt 1.x docs, but I'm also adding new materials like "Why sbt exists" page https://www.scala-sbt.org/2.x/docs/en/#Scala#sbt
PRO-TIP: #ScalaCLI can compile packages with #GraalVM's native-image. And without --no-fallback, the compatibility issues (e.g., w/ reflection) are minimal.
Fast startup, reasonable binary size, good RAM use 💪
I got a #Scala class to teach in May. I love teaching Scala. However, what is interesting now is that I am teaching programmers who are already used to Java Streams. They know their map, flatMap, and filter. That is going to cut down on time, and that leaves space for bigger and better things. We will see how it goes.