To me, it shows that optimizing performance is, most of the time, fixing a problem that doesn't exist.
I'm glad that Angular introduced all these signals-related changes, but mostly because of the improvements they bring in DX, not so much about the better performance they allow.

Also, developers start from this idiom (kotlinlang.org/docs/idioms....), and then try to find a way to add an else block to it.

What I mean is that `val foo = condition ? bar : baz;` is shorter than `val foo = if (condition) bar else baz;`, so developers tend to try to find (often less readable and more bug-prone) alternatives.

The absence of the classic ternary operator in Kotlin is probably one of the reasons for this. One of the cases where Kotlin is more verbose than Java.