After experimenting with @Zed a couple of months ago, I have now finally ditched @IntellijJ for good. And it's awesome! So awesome that I need to share it with you, sorry π
Matej Cerny
npub17hpl...yx66
Functional programming enthusiast with strong foundations in the relational databases world #FP #Scala #Postgres
Spark 4.0 is official! π Scala 2.13 and JDK 17 are the new defaults! It also supports the SQL pipe syntax, so you can do e.g. 'FROM customer |> JOIN orders ON ... |> AGGREGATE COUNT ...' #scala #spark #sql
Spark Release 4.0.0 | Apache Spark
Fill in this survey if you want Scala to be more recognized. Just a heads-up, it's looong! It took me half an hour to finish it. #scala 

Developer Ecosystem Survey 2025
Take our survey, shape the future, and seize the chance to win a MacBook Pro or other rewards!
Keeping an eye on this project! π #scala 
GitHub
GitHub - TomasMikula/jing: Typesafe, spec-first APIs without codegen. Just Import 'N' Go!
Typesafe, spec-first APIs without codegen. Just Import 'N' Go! - TomasMikula/jing
What an incredible lineup! #scaladays
Scala Days
2025 Schedule
The premier Scala conference returns in 2025
That might be an unpopular opinion, but I really don't mind adding an import when concatenating e.g. a List with an Array. But I would rather remove the restriction on implicit conversions than add another keyword. #scala 

Scala Contributors
Pre-SIP: Allow fully implicit conversions in Scala 3 with `into`
Thank you all for your input. That was very helpful improving the proposal. I believe the overall appreciation tended positive so I went ahead and ...
Despite not being a VS Code user, this Postgres extension looks great! I would really like to see it in Zed! #postgres #vscode 
TECHCOMMUNITY.MICROSOFT.COM
Announcing a new IDE for PostgreSQL in VS Code from Microsoft | Microsoft Community Hub
We are excited to announce the public preview of the brand-new PostgreSQL extension for Visual Studio Code (VS Code), designed to simplify PostgreS...
Even though it's still in the pre-alpha phase, it's a huge step forward for Kotlin! The official LSP by JetBrains! π #kotlin 
GitHub
GitHub - Kotlin/kotlin-lsp: Kotlin Language Server and plugin for Visual Studio Code
Kotlin Language Server and plugin for Visual Studio Code - Kotlin/kotlin-lsp
Of course I had pizza for dinner! π Happy ATH to everyone! π #bitcoin #ath
Let's say you are a Java developer looking to take the next step and fully dive into functional programming. Don't be scared of Scala's syntax! Take a look - it's often more familiar than you might think! #java #scala #functionalprogramming


Soon I will become a farmer! π β
install Vim plugin to IntelliJ β
buy a split keyboard β
install LazyVim β configure Neovim from scratch
The new version of the IntelliJ Scala plugin is out. Now you can use the "better-fors" syntax from Scala 3.7! β€οΈ #scala https://plugins.jetbrains.com/plugin/1347-scala/versions/stable/748379
Not sure if I am comfortable with the current pace of innovation π€―
The truth is, if you learn functional programming, then it doesn't matter what language you use, as the fundamental principles are transferable to any of them. View quoted note β
Did you know that there is also a Kotlin version of the famous Red Book? π #functionalprogramming #kotlin 

Manning Publications
Functional Programming in Kotlin - Marco Vermeulen, RΓΊnar Bjarnason, and Paul Chiusano
Master techniques and concepts of functional programming to deliver safer, simpler, and more effective Kotlin code.
With the deprecation of the Sonatype OSSRH API, support for publishing artifacts to Maven Central is moving directly to sbt! It looks like there will be no need for sbt-sonatype plugin anymore. Unfortunately, sbt-pgp is still required. #scala
sbt 1.11.0-RC2 · eed3si9n
If you haven't seen it yet: View quoted note β
"Speed up your editing, speed up your thinking." #vim
Next time you hear there are no advantages to upgrading to Scala 3, feel free to share those examples π #scala


The first two tips are imo the most important. While everyone wants to try the new syntax, it's best to handle the breaking changes first (mostly codecs), go to production, and leave the fancy new stuff for the next iteration after things have settled down. https://nitter.net/kopaniev