<https://kotlinlang.org/docs/collections-overview.html#map> Why is it designed in this way? what be...

# getting-started

[anlex N]

https://kotlinlang.org/docs/collections-overview.html#map

Why is it designed in this way? what benefits?
Thread in Slack Conversation

[Ruckus]

This is for Java, but the same reasoning holds for Kotlin: https://stackoverflow.com/a/2651833

[anlex N]

so you can not say it's a Kotlin collection type as well. please update docs.

[Ruckus]

It is a "collection type" in the everyday sense, it's just not a Collection in the API sense. The distinction is a bit arbitrary unfortunately, but it's a legacy that has been that way on the JVM for decades, so it's a bit too late to change.

[anlex N]

so crazy. That's not how innovation works.
I think Java have been corrupt, have no little innovation in many years.

[Ruckus]

Innovation doesn't mean there's no legacy. And I would counter Java has had a significant amount of innovation in recent years, and there's more coming down the pipe all the time. Look through recent release notes to see all the features and enhancements that have been added, and check out some of the things currently being tested and prototyped for future versions.

[Ruckus]

Regardless of your feelings toward Java, Kotlin still needs to hold true to its promise to be 100% compatible with Java, which does mean inheriting some of its legacy.

[anlex N]

@Ruckus please see [this thread](https://kotlinlang.slack.com/archives/C7L3JB43G/p1709974512257379)

[Ruckus]

I have nothing to add to that thread