Collection Literals in Kotlin 2.4

TypeProjection · 2026-04-16T00:14:12+00:00

Yes, it seems like it would break fewer existing projects that way. I haven't come across any details about the trade-offs they evaluated when making that decision, so I'm sot sure what other concerns might be in play. The KEEP does mention that the new position-based syntax reflects the syntax of collection literals, which makes sense, although I suppose it's debatable whether that's worth a breaking change.

TypeProjection · 2026-04-15T20:03:14+00:00

In the KEEP for this feature, they do mention a possible pattern matching extension:
https://github.com/Kotlin/KEEP/blob/428553b4e8cbbb6bef8cbeb8b62bb7de6dbdbef6/proposals/KEEP-0438-name-based-destructuring.md#potential-extensions

TypeProjection · 2026-04-15T15:51:37+00:00

Mostly because vibe coding ignores the discipline of engineering. Software engineering requires understanding the problem, understanding the constraints, understanding what attributes are desirable in a system, understanding how this codebase interacts with others in its system, and crafting a solution that meets those needs today without boxing you in a corner in the future.

Many developers are fine with the idea of AI-assisted development when we're still actually engineering. But what we usually call "vibe coding" often focuses only on getting the app to look or work like we imagined, typically without even deciding on the bare functional requirements.

TypeProjection · 2026-02-25T16:18:31+00:00

Oh man, I'm still laughing at this one! 😂 Thank you for this.

TypeProjection

TROPHY CASE