Steve Tian 🇺🇦🌻🇹🇼

Developer by day, Developer by night.

[Kotlin by JetBrains @kotlin]

📢 Kotlin 2.4.0 is out! Here are some of the highlights:
✅ Language: Stable context parameters, explicit backing fields, and multiple features for annotation use-site targets.
✅ Standard library: Stabilized support for the UUID API and support for checking sorted order.
✅ Kotlin/JVM: Support for Java 26 and annotations in metadata enabled by default.
✅ Kotlin/Native: Support for Swift packages as dependencies, updates on Swift export, and the CMS GC enabled by default.
✅ Kotlin/Wasm: Incremental compilation enabled by default and support for WebAssembly Component Model.
✅ Kotlin/JS: Support for value class export and ES2015 features in JS code inlining.
✅ Gradle: Compatibility with Gradle 9.5.0.
✅ Maven: Automatic alignment between Java and JVM target versions.
✅ Kotlin compiler: More consistent inline function behavior during .klib compilation.
Learn more: https://t.co/8cT1Jicklk

[Siva @sivalabs]

I just want to log some value temporarily for debugging purpose. Can I do it without adding log statements in code?

YES.

While I am already running the app?

YES.

Without restarting the app?

YES.

Even in 3rd party code?

YES.

https://t.co/EMfGRXOzM1

[JetBrains @jetbrains]

Understanding code is a big challenge in the AI era, which is why our colleague @forketyfork has built Walkthrough.

This experimental plugin gives AI agents an MCP tool for walking you through code in a JetBrains IDE in a visual way rather than using walls of text.

Check it out: https://t.co/LZbp5p0PDM

[The Micronaut Framework @micronautfw]

We are pleased to announce Micronaut 5.0.0-RC1 – a release candidate. 
https://t.co/Eoc3oachg5
Please try the release and report any bugs before it goes GA within the next few weeks. 

To help with upgrading, a migration guide is available.
https://t.co/zEuoAy9YuH #micronaut

[LocalStack @localstack]

LocalStack for AWS 2026.03.0 is out and it represents a major shift in how LocalStack for AWS is released including a move to a consolidated Docker image, calendar versioning, no CI credit limits, a new CLI and much more! Get all the details here 👉 https://t.co/foHphq9det

[The Micronaut Framework @micronautfw]

The Micronaut Foundation is excited to announce the release of Micronaut Framework 4.10.10! Please see our latest blog post for more details. https://t.co/Z1cIRi78Xl #micronaut

[Alejandro Serrano @trupill]

New @kotlin language proposal: companion blocks and extensions https://t.co/vMYep7ZGTU

Feedback is more than welcome!

[Gwen (Chen) Shapira @gwenshap]

⚠️PSA: Don't use Docker's official Postgres image in production.

Or, if you do, make sure you specify your Debian image.

The long version:
Postgres minor version upgrades (17.6 -> 17.7) are generally easy, safe and recommended. They should never break anything.

*But* if you use the official docker image and recently (since August) did a minor version upgrade, you may have seen this warning:

"The database was created using collation version 2.36, but the operating system provides version 2.41.
Rebuild all objects in this database that use the default collation and run ALTER DATABASE "mydb" REFRESH COLLATION VERSION, or build PostgreSQL with the right library version."

This is because:
- Docker only supports 2 debian versions for the PG image
- When a new version comes out, it automatically becomes the default unless you specify the image.
- Debian's new release included a new glibc, which includes new locale files.
- So now you are running Postgres linked against one set of locale files, but with a database with data and indexes that assume a different locale file.

Since this situation can lead to anything from bad query results to corruption, Postgres correctly warns you to refresh the collation for the DB, which you do *after* rebuilding every object in your database (to avoid corruption).

This is something we do on **major** upgrades, and absolutely do not expect on **minor** upgrades.

But Docker forces this on the users of their official image.

Be careful out there! Official image does not mean "responsible production behavior".

[Roman Elizarov @relizarov]

Great news! This fall, I’ll join Coroutines Mastery, a new cohort-based course on Kotlin Coroutines from @ktdotacademy. I’ll be hosting two live Q&A sessions with participants. Hope to see you there!

[Márton Braun (write-only account) @zsmb13]

New Kotlin video! Context-sensitive resolution is one of those features that will kind of quietly blend into the background while making a lot of code much nicer. And you can already try it in Kotlin 2.2 as an experimental feature!

Check out the details:
https://t.co/EpGWAqAM7z

[Tower @gittower]

Git Blame knows a lot, but have you ever wanted it to ignore those annoying formatting changes and refactors?

Learn how in this blog post 👉 https://t.co/Zu9JMKy1rI

[The Micronaut Framework @micronautfw]

The Micronaut Foundation is excited to announce the release of Micronaut Framework 4.9.0 ! Please see our latest blog post for more details. https://t.co/sVJF31L1bH #micronaut

[Sam Brannen @sam_brannen]

#JUnit 6.0.0-M1 is ready for testing! 😎

✨ Requires Java 17 and Kotlin 2.2
🌄 JSpecify nullability info
🚟 Kotlin suspend function support
🛫 Integrated custom JFR events
🚅 FastCSV-backed Csv{File}Source
🧹 Removed deprecated APIs and behaviors

https://t.co/LBAXZK1P7G

[jacob paris ▲ @jacobmparis]

TIL localhost can have subdomains

[DuckDB @duckdb]

The DuckDB v1.3.1 bugfix release is out:
https://t.co/5HY0CAjmrw

As usual, the CLI, Python, C and C++ clients are already available. We will roll out the other clients over the coming days.

[Dmitrii Smirnov @dvsmir]

Working on improving Gradle scripts completion in @intellijidea . WDYT?

[DuckDB @duckdb]

We released DuckDB 1.0.0 a little over a year ago with a small easter egg. Since then, no one reported finding it, so we're revealing it: the hash of the DuckDB 1.0.0 binary starts with the duck emoji: 0x1f986 = 🦆.

[Sam Brannen @sam_brannen]

#JUnit 5.13 is here!

🪄 ClassTemplate & @⁠ParameterizedClass support
⚠️ Discovery issue reporting
♻️ Resource management for launcher sessions and execution requests
🔍 Test discovery support in EngineTestKit
👾 ConsoleLauncher improvements

https://t.co/6B48l1vkhE

[Sam Brannen @sam_brannen]

The #JUnit team is looking for ideas and proposals for a new #logo for the upcoming JUnit 6.0 release!

For ground rules, please see: https://t.co/xVLPaXfieZ

We are looking forward to your comments and submissions! 💡

[Josh Long @starbuxman]

Every one of Arjen’s posts represents years of API design in action, invaluable guidance

https://t.co/DOKYlPY7O3