RustCon

The only conference in Russia for Rust developers and who concerned.

December 3rd, 2021, Moscow
Talks formats
We are looking for interesting talks and people who have something to say.
Keynote
Keynote is a large-scale 60 minutes presenation when we will talk about Rust 's future and present.
Talk
Talk is a classic format with 30-40 minites duration.
Lightning Talks
5-minute talks where everyone can have a word.
Workshop
Workshop is 1,5 – 2 hours of working on task or theme to learn something new. Workshop consists of theoretical and practical parts. It is the format with the most complete coverage of the topic.
Sprint
Sprint is a multi-hour training and open source project work format with the project author and other participants.

We`re waiting for talks in all aspects of Rust for the middle and advanced levels. Also hope to find workshops authors and mentors for sprints.

List of Ideas for RustCon2021
The list is opened to all new suggestions. We`re waiting for your brilliant idea!
About Rust
First of all, we are interested in talks about Rust itself: where everything`s going and what to exptect from future releases.
Main purpose is to show that Rust is a good language for everyday use.
API-scope

Python and Go are regulary used to create API because it`s simpler and faster. Could Rust be competitive in this field? and is it really necessary? Hoping to find speakers with practical experience of creating API in Rust: its speed compared to other languages, also presentations about Rust infrastracture and maturity.

OSDev
The development of both OS and modules for it is painstaking and complex work. However, we do believe the community advances in popularizing the Rust will help to improve and stibilize new methods. In this section, we`d like to hear talks about: Rust for Linux kernel, drivers for different OS, Redox ecosystem and its design etc.
Embedded/no-std
There has been The Working Group on Embedded Devices since 2018. They are supporting Rust for various "small forms" - microcontrollers, various SoC. How is the situation in this field? What's new in tooling, maintenance for microarchitectures? Is Rust able to compete with classic C? Do Rust's capabilities provide additional advantages in microcontroller development - security, reliability, static guarantees? Can Rust live without std? What's with async support?
WebAssembly and Rust in Front-end
Front-end development is almost synonymous with JS, but the popularization and improvement of WebAssembly allows other languages ​​to enter this niche. How ready is the Rust / WASM ecosystem and tools for production? What should you be aware of when reusing back-end Rust code? Do dotting Rust libraries in JS projects justify themselves to optimize bottlenecks? In what projects does it make sense to try to completely "oxidize" the front-end? Can WASM be used outside of web development?
Cryptografical libraries at Rust ecosystem
An important area of ​​systems development is cryptography, where Rust does its best. On the one hand, it provides high performance, on the other hand, it provides a guarantee of safe work with memory. In this section, we want to hear about experience of implementing cryptographic libraries and applications. How ready is the Rust crypto ecosystem in general? Are there any significant advantages of Rust, or the development efficiency does not differ much from the C?

Incremental rewriting of projects in Rust
The one-time Rewrite-it-in-Rust of a serious project looks like a tempting adventure, but usually too risky. Due to its low level and lack of a thick runtime, Rust allows you to port large native projects piece by piece. How difficult is it to implement it in practice and does it lead to the expected positive effects? How to organize cross-testing and reduce the risk of diverging from the original?
Supporting tooling
Since its release, Rust has been accompanied by high-quality tooling, and every year the number and quality of auxiliary tools has been growing - from the well-known cargo-edit / rust-analyzer to advanced / niche pieces in the spirit of cargo-miri / cargo-fuzz / xargo / tokio-loom. What is interesting about the arrangement of such instruments? What little-known tools are worth paying attention to and how useful are they in practice?
Distributed Rust Applications
Solutions and ecosystem overview
Tokio vs async std
Review and improvement of each of the frameworks
Results of the work of various WGs and plans for the near future
Essay outline
Usually there are more suggestions than we can take into the program, so describe your future talk as much detailed as possible.
Task
Task
What was your task? Why was it difficult?
Explanation
Explanation
Why do you pick this tool, method or library to find a solution?
Process
Process
What problems did you face, how did you solve them?
Solution
Solution
How was the problem solved in the end?
Applicability
Applicability
Pros, cons, pitfalls of this solution?
Audience
Audience
Who is the essay for? What tasks can people who are interested in listening to it work on? What problems do they face in their work?
Profit
Profit
What will the audience learn after your talk?

The Program Committee accepts applications until November 15th, after which conference program will be formed.

Program Commitee
These are the guys who invite speakers, review suggestions and choose the most valuable and fascinating talks. Also, they help speakers to get ready for the conference, arrange rehearsals of the keynote talks, and do their best to make an awesome program
Shagit Ziganshin
BestDoctor
Andrey Ermilov
Avito
Maxim Belousov
Rambler&Co
Anton Patrushev
Spherical
Evgeny Minibaev
Квантом
Andrey Lesnikov
JetBrains
Call for papers
Name
E-mail
Country/City
Tell about yourself
Company, position, achievements, links to a blog or profile, links to past talks, if you have any.
Subject of your talk
What would you like to talk about? Describe your talk
Who is this talk for?
For example, The talk is good for developers and team leaders who already use this technology in their projects or do not use it, but want to start.
What useful ideas can people take from your talk?
Write down at least one thought. For example, "Listeners will be able to understand whether this solution is suitable for their tasks and whether it is worth reading detailed documentation", or "Listeners will be able to understand when to use such a solution so as not to harm the project in the future."
Your favourite messenger
Phone
Are there any awesome speakers you would like to recommend?