Been having fun with #gleamlang , made more than a hundred lines of code with it. It's really refreshing having a language that compiles fast and takes barely any memory and cpu to run.
Not having to care about the build tool too much, hundreds of compiler flags, language versions, compiler plugins, formatting plugins, or any of the usual things that fill the brain I'm used to in #scala is a huge breath of fresh air.
The syntax sometimes is not very pretty (subjective). Functions receiving functions as parameters get a bit ugly with 'x |› map(fn(v) { ““ })' feeling like having too many parentheses.
#Scala syntax is prettier in this aspect with
'x.map { v =› "" }’ being more lightweight.
And formatting sometimes doesn't do what I'd like.
And I dearly miss the 'for { y <- stuff } yield ""' syntax. The 'use syntax' doesn't really click with me yet.
Ten years down the road, the most annoying thing in Javaland remains troubleshooting these dynamically detected logging systems and their various runtime errors. Digging into classloader issues and the contents of META-INF. 😠
Really appreciating the Scala approach to do (and check!) everything at compile-time.
cool thing about playing with #gleamlang is that it actually runs on my laptop without making it hot and putting the fans in crazy mode.
compiles and runs fast, few MBs of memory.
creating a binary with gleescript creates a script that makes the application run on erlang vm and it works without much ceremony and again without killing my memory and taking all my swap space.
it's a nice change of pace compared to the usual #scala that can't run without 4 jvm processes killing the machine 🙄
Just released another version of the Smederee - your friendly darcs forge. 🤩
Your organisations are now shown on your user settings page and they are more easily edited. Also owners can delete organisations now. Adding administrators to an organisation is still on the todo list though. 😉
#ScalaCLI v1.2.1 is out now! Along with support for #Scala 3.4.1 & Scala.js 1.16.0.
That, and the regular stream of minor enhancements and fixes.
Check the release notes here
I'm currently finishing "The Heart of Salamanderland" for the Amstrad CPC, that will have a physical release by PolyPlay (see my Brick Rick for an example!).
the xz situation, which is too real for me, is a reminder for #Scala community that Zinc, sbt, and many of plugins are maintained in my free time (which is by design, and works while it works)
if your company uses #Scala at work, consider joining Scala Center corporate membership (50k/yr or 15k/yr), or provide % of eng time to them. for these toolchains, Scala Center is often the organization to fix CVEs, alongside compiler stewards like VirtusLab and Lightbend https://scala.epfl.ch/corporate-membership.html
I love the ideas in #Erlang, but I’ve never quite gelled with the language. So when I heard someone was porting the runtime to #OCaml, my ears pricked up.
Leandro Ostera joins me this week to explain how he's borrowing BEAM's best bits. 😅
On #scala we have akka library/system for actors, for many years working, so anyone looking into actor systems should definitely check it out too even if just to compare the patterns/design considerations.
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