Yet adopting a new language is a complex process, and not one to be taken on lightly; there are many trade-offs involved from hiring and training to compatibility and maintenance. Rust is not the right answer to every problem everywhere, nor is *now* necessarily the right timing for you. And unfortunately, it can be difficult to assess the trade-off space in adopting Rust without significant experience on both sides of the fence: both in Rust and in the technology you work with today.

So, we're bringing together a panel of experts to discuss when, where, and why Rust is, and isn't, appropriate, based on their experience across languages and domains. Their goal is to help separate myth from fact, critically evaluate where and how Rust can deliver value in practice, and answer questions people may have that make them uncomfortable with the idea of adopting the language.

These kinds of panels work best when they help the audience answer *their* questions, so please do submit questions in advance to the panel host at TODO.