About Mojo native support for disk io, networking, gui and threading

[lijh8]

Will Mojo have native support for:

• disk file io (fopen, fgets, ..),
• networking (socket, epoll, boost.asio, python asyncio, ..),
• gui (tkinter, gtkmm, Qt, ..),
• multiple threading,
• portability across PC, Server, mobile, ..
• etc..

[ksandvik]

See 0.4 release notes where there's an initial file I/O module: https://docs.modular.com/mojo/changelog.html#v0.4.0-2023-10-05

[rarebreed]

Mojo is still very very young. It doesn't even have a native dict/map type yet :)

It would be nice if there was a list of functionality they want in their stdlib. Will mojo be "batteries included" like python? Or more lean like rust? Will they have async forms from the beginning, or tack it on later like rust and python did? This is a significant question, because in both rust's and python's cases, they have competing non-standard async versions of common modules. In rust, tokio vs async-std, and in python, async vs trio vs anyio.

[lijh8]

How about make python a static typing language by introducing type inference. This will not break existing code. eg:

a = 123 # inferred as int
a = “hello” # re-defined as string
a:float = 123 # type annotation 

[ksandvik]

Interesting point. My take/opinion is single supported libraries based on open-source contributions/work. If someone then wants to make alternate libraries, that is fine, too, but it's outside the Mojo umbrella. Anyway, just an opinion.

[rarebreed]

My fear is that by not having an async "standard" module, you can make incompatible ecosystems where library foo uses my-async-network and lib foo has a transitive dependency that uses another-async-network lib and they are incompatible with each other. Indeed, anyio is supposed to be able to handle plain old native async libraries like aiohttp, as well as trio style nurseries.

I also mention this, because in rust, there is a problem with async scoped concurrency that really didn't come to light earlier because they tacked on async later in language development.

[richardkiss]

See also Chris's response here #1147