is there somewhere a write up/discussion about the...

# language-proposals

[Vladyslav Sitalo]

is there somewhere a write up/discussion about the decision to make the dynamic type available only on the js platform? From what I’m reading for now it seems to be that it was not supposed to be like that initially (i.e. here: https://discuss.kotlinlang.org/t/dynamic-type/1145)

[Vladyslav Sitalo]

I think this needs more different emoji reactions 😛

[karelpeeters]

You kind of need it when interfacing with existing JS code, right?

[Vladyslav Sitalo]

oh, I’m not asking why is it there for js. I’m asking why is there only for js.

[karelpeeters]

?? Why would you actually want that on other platforms?

[Vladyslav Sitalo]

For all the same reasons people like dynamic languages? 🙂
I like kotlin type system and most of the time it’s not constraining. But having an option of having more flexibility at select times can be beneficial. Especially when you are doing some metaprogramming/etc

[elizarov]

Dynamic typing is like a plague. JS ecosystem is already sick, so often interfacing with JS ecosystem requires dynamic typing. If you bring it to other platforms, then you’ll irreparably infect the corresponding ecosystem. Look at the whole Groovy/Gradle ecosystem. That is dynamic typing on JVM. Learn from their mistakes. Don’t be like them.

[Vladyslav Sitalo]

@elizarov Any specific links/articles you’d advise to look at ? 🙂

[elizarov]

There are tons of articles on static vs dynamic typing (though less so on negative ecosystem effect of dynamic typing). I cannot point to any particular piece that I would recommend to read.

[deviant]

Why would you actually want that on other platforms?

Just my guess: to write prefs.user = "John" instead of prefs["user"] = "John"