@olonho What we can expect in future stdlib? Does it make sense to expect file/networking io, concurrency and http/http2 in stdlib or cinterop (eg: curl for http) is the way going forward??

suresh: this topic is being discussed, but I would suggest cinterop for now. This is how Kotlin/JVM works as well, and I personally find a nice language (Kotlin) for existing well tested libraries more appealing than a universal standard library trying to cover the whole world.

This is probably the better approach. Python has an HTTP module in the standard library, but to preserve compatibility the API can't evolve, so everyone uses a third-party alternative anyway. Java has three different built-in UI frameworks, all of them terrible, bloating the platform but providing little value. I prefer a small core with excellent interop.

if the std lib is modulable then it would be nice to have stuff out of the box 😛