Skip to content

Add missing "platform" #1785

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 25, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion blog/_posts/2025-03-24-evolving-scala.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down