I was pointed out yesterday to scodec for #scala. It has some important things there that seem very useful and will likely use it.
It's just pretty sad that such a known, useful, stable library has most of the site with incomplete docs, broken links and incomplete released version numbers.
I'm reading this book on #Scala now and what can I say so far about the language, is that it can be summarized as ‘best effort to create a decent functional language given the limitations of JVM’. https://www.goodreads.com/book/show/13541678
#ScalaCLI v1.3.0 is out! We have added support for Scala Native 0.5.1, which will now be the default version used by the CLI on the --native platform. Regarding #Scala Native, take note that some tools which Scala CLI integrates with are not yet available on Scala Native 0.5.x.
Async/await in #TypeScript is essentially “direct style”. It will be interesting to see if Effect, a monadic effect system, will take off, as a case study for #Kotlin & #Scala — although for “direct style”, these have the advantage of context parameters.
After a solid month or two of engine improvements, my little #Scala ASCII paint app looks like it did before! 💪
However, all the UI stuff now runs in a subsystem and all the layers are nested under one key, making the app logic far, far simpler. New Indigo release coming soon...
A weird thing about being 50 is that there are programming languages that I've used regularly for longer than some of the software developers I work with have been alive. I first wrote BASIC code in the 1980s. The first time I wrote an expression evaluator--a fairly standard programming puzzle or homework--was in 1990. I wrote it in Pascal for an undergraduate homework assignment. I first wrote perl in the early 1990s, when it was still perl 4.036 (5.38.2 now). I first wrote java in 1995-ish, when it was still java 1.0 (1.21 now). I first wrote scala, which I still use for most things today, in 2013-ish, when it was still scala 2.8 (3.4.0 now). At various times I've been "fluent" in 8086 assembly, BASIC, C, Pascal, perl, python, java, scala; and passable in LISP/Scheme, Prolog, old school Mathematica, (early days) Objective C, matlab/octave, and R. I've written a few lines of Fortran and more than a few lines of COBOL that I ran in a production system once. I could probably write a bit of Haskell if pressed but for some reason I really dislike its syntax so I've never been enthusiastic about learning it well. I've experimented with Clean, Flix, Curry, Unison, Factor, and Joy and learned bits and pieces of each of those. I'm trying to decide whether I should try learning Idris, Agda, and/or Lean. I'm pretty sure I'm forgetting a few languages. Bit of 6502 assembly long ago. Bit of Unix/Linux shell scripting languages (old enough to have lived and breathed tcsh before switching to bash; I use fish now mostly).
When I say passable: in graduate school I wrote a Prolog interpreter in java (including parsing source code or REPL input), within which I could run the classic examples like append or (very simple) symbolic differentiation/integration. As an undergraduate I wrote a Mathematica program to solve the word recognition problem for context-free formal languages. But I'd need some study time to be able to write these languages again.
I don't know what the hell prompted me to reminisce about programming languages. I hope it doesn't come off as a humblebrag but rather like old guy spinning yarns. I think I've been through so many because I'm never quite happy with any one of them and because I've had a varied career that started when I was pretty young.
I guess I'm also half hoping to find people on here who have similar interests so I'm going to riddle this post with hashtags:
#scala be like: oh no, ecosystem is too broken with many silos, 3 different effect libraries is too much, people can't decide, monads are too hard...
Scala solution: let's introduce a whole new thing called direct style, there's now 7 new libraries, competing against the previous 3 and std Futures. We are even working on effect things in a different way which will introduce 2 more ways to think about it!
Everybody else: yeah, tks but no, don't what deal with that craziness 😱😐
After hearing good things about scalatags, reading the readme I almost walked away when I saw the changelog with latest version being 0.7.0 adding support for scala 2.13. I was literally thinking it was dead and nobody worked on it for #scala 3 for example... 😮💨
Well turns out that if you open github you see that it actually was tagged a version 0.13.1 and the changelog hidden in a file is getting updated.
But the official docs website doesn't have any recent updates! 😨
As changes piled up and deploying them is more or less instant I've tagged version 0.12.0 of the Smederee! 😀 🎉
Most noteable changes are base work for organisations and fixes of broken source tarball downloads and incorrect reset password links. For more details see the changelog: https://smeder.ee/~jan0sch/smederee/files/CHANGELOG.md
The unfortunate thing about the downfall of corporate #scala was that #scala3 was actually pretty good. By the time it finally arrived companies didn't want to migrate.