-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewrite the Introduction chapter #61
Conversation
Looks good to me, already! Not sure if we really need to answer "Why Should I use Rust on ESP?" here, since the user who got here is probably already interested in doing that? |
I think it would be beneficial to have some kind of "what advantages does this approach have?" section, maybe with a pointer to https://www.rust-lang.org/what/embedded and a few details should be sufficient |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commented on small details, they are more questions being raised than comments. Feel free to address them! Also, maybe we should include a link to our matrix channel and Awesome ESP Rust repo (?)
Gonna just merge this for now, if we decide to go through with adding a section about the benefits then that can be handled in a separate PR. |
* Remove the "Resources" and "Glossary" pages * Rewrite most of the introduction chapter * Address review comments
* Remove the "Resources" and "Glossary" pages * Rewrite most of the introduction chapter * Address review comments
Leaving this as a draft because I haven't answered the "Why Should I use Rust on ESP?" question yet, and because I would like to get some feedback on the work that I have done.
This is heavily inspired by The Embedded Rust Book.
Also got rid of some pages that we decided aren't required. The content will be covered elsewhere in the future.
Rendered view: https://github.com/jessebraham/book/blob/59c3b9470bc9791e1fabe031e2d4f493ad508eeb/src/introduction.md
@SergioGasquez @MabezDev @bjoernQ @JurajSadel @georgik if any of you have any input on this I would love to hear it! Are we missing anything? Anything we could explain better?