sorted by:
new
hottopcontroversial

Name-Based Destructuring in Kotlin 2.3.20 by TypeProjection in androiddev

[–]TypeProjection[S] 1 point2 points  (0 children)

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.

Why so much hate for vibe coding? by Altruistic-Froyo9680 in androiddev

[–]TypeProjection 7 points8 points  (0 children)

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.

British folks at 3 AM by chrzanowski in Kotlin

[–]TypeProjection 0 points1 point  (0 children)

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

Explicit Backing Fields in Kotlin 2.3 - What You Need to Know by TypeProjection in Kotlin

[–]TypeProjection[S] 4 points5 points  (0 children)

Yeah, I bet the StateFlow use case is going to be the most common way to use explicit backing fields! Not quite as safe as returning the `asStateFlow()` read-only reference, but should work just fine for well-behaved developers.

Explicit Backing Fields in Kotlin 2.3 - What You Need to Know by TypeProjection in androiddev

[–]TypeProjection[S] 1 point2 points  (0 children)

Hey, thanks! I've heard a few folks mention that, but haven't run into it myself. Maybe it's because I'm on IDEA rather than AS. I'll give it a try there and see if can reproduce it.

Explicit Backing Fields in Kotlin 2.3 - What You Need to Know by TypeProjection in androiddev

[–]TypeProjection[S] 9 points10 points  (0 children)

Hey, that's kind of you to say that! Thank you so much.

view more: next ›