Above poster is talking about thinking in terms of grouped lifetimes and bulk allocations/deallocations, which is better for performance, and makes Rust borrow checking and other RAII style features pointless as they don't add any safety benefits. This video completely changed the way I think, and I subsequently moved on from Rust: https://www.youtube.com/watch?v=xt1KNDmOYqA

This is true, he talked about this recently in a livestream: https://www.youtube.com/watch?v=mQh9es5gfpo

Disclaimer: I work for Modular

Then why not just be open source from the start?

What benefits does one get from starting off closed and transitioning to open source?

Maybe you don't want the peanut gallery commenting/complaining/whatever about your architecture until you are ready (otherwise architect astronauts could inundate your comm channels with suggestions, comments, PRs, etc)

Hi, thanks for your interest! You can opt out of telemetry if you like. Please see the FAQ here: https://docs.modular.com/mojo/faq.html#does-the-mojo-sdk-col...

For open sourcing, we also have a section in our FAQ: https://docs.modular.com/mojo/faq.html#open-source, and we answered a question about that in the latest livestream! https://www.youtube.com/watch?v=mQh9es5gfpo

For the question on pricing, the Mojo SDK is free to use.

Disclaimer: I work for Modular

0:16 from https://www.youtube.com/watch?v=mQh9es5gfpo, says "we'll be open sourcing documentation"... by the end of the year. Documentation? It will have taken a full year to open source documentation. Congrats.

That's disingenuous. They are also open sourcing the standard library by the end of the year.

Soo maybe some "core" "parts" might be open sourced some time. Hard pass.