From 27c1eb65e89e11d63874370915394aa67ea6dcf0 Mon Sep 17 00:00:00 2001 From: Philippus Baalman Date: Tue, 25 Mar 2025 13:45:48 +0100 Subject: [PATCH] Add missing "platform" --- blog/_posts/2025-03-24-evolving-scala.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/_posts/2025-03-24-evolving-scala.md b/blog/_posts/2025-03-24-evolving-scala.md index de335f1ef..bb39a3971 100644 --- a/blog/_posts/2025-03-24-evolving-scala.md +++ b/blog/_posts/2025-03-24-evolving-scala.md @@ -36,7 +36,7 @@ Although individuals in the community come and go, Scala as a whole seems to be Technically, Scala is on stronger foundations than it was 10 years ago. The ecosystem has matured and the various Reactive or Pure-FP styles have found their audiences. -Alternative styles like the [Scala Toolkit](https://docs.scala-lang.org/toolkit/introduction.html) and the [com.lihaoyi](https://github.com/com-lihaoyi) are now available. +Alternative styles like the [Scala Toolkit](https://docs.scala-lang.org/toolkit/introduction.html) and the [com.lihaoyi](https://github.com/com-lihaoyi) platform are now available. New build tools like [Scala-CLI](https://scala-cli.virtuslab.org/) and [Mill](https://mill-build.org) have emerged, and developer tools like [Scalafmt](https://github.com/scalameta/scalafmt) and [Scalafix](https://github.com/scalacenter/scalafix) have become widely used. IDEs remain a pain point, but we expect them to improve over the course of 2025. Heavy use of symbolic operators has thankfully fallen out of style.