They include debug info in release builds in their configuration.
If you run `strip` on the resulting binary, it will likely drop to like 5 MB.
1,186 karma · joined September 26, 2016
They include debug info in release builds in their configuration.
If you run `strip` on the resulting binary, it will likely drop to like 5 MB.
It's not as slick as the "swap batteries, now you're fully charged", but on the other side, the USB batteries can charged without the laptop, and you can pick the size you're willing to carry around.
Parallelism is for many things working at the same time. Concurrency is for many things waiting at the same time.
Because the situation with COVID-19 is causing issues with conferences and events around the world, we wanted to provide a chance for folks to interact from home. Oxidize 1K isn't replacing the main Oxidize Conference, but we're trying out new things, just in case!
We've also opened our CFP[0] if you'd like to submit a talk, it'll be open until 8AM CET on Monday!
Happy to answer any questions :)
Edit: they followed up this year as well, still using Rust: https://www.reddit.com/r/rust/comments/cdg5b4/rust_in_the_on...
NPM also has a white paper on their choice to move parts of their Backend Services to Rust as well.
Cryptography is certainly an interesting target - they certainly could benefit from the specification of the language, despite not being legally required similar to the other domains listed here.
Feel free to reach out at sealed-rust at ferrous-systems.com!
Check out https://github.com/ferrous-systems/embedded-trainings/blob/m...
OxidizeConf[0] is the first conference focused on Embedded Rust, and we've just announced our (almost complete) speaker list! The conference will be April 26th-29th in Berlin, and it would be great to see you all there!
My company, Ferrous Systems[2], is also focused on embedded systems development in Rust, and we are already helping companies both with embedded linux and bare-metal/RTOS projects in Rust.
We're also running a conference in Berlin on April 26th-29th called OxidizeConf[3] if you are interested in learning more about what is already going on in the Embedded Rust world :)
[0]: https://github.com/rust-embedded/wg
[1]: https://github.com/matklad
Author of the first link above. The Teensy3 crate was some of my first embedded work, I was working with SimonSapin (author of the 4th link) at RustFest to get something working. That library wraps some of the Teensyduino code using bindgen, which gives you the ability to write application code using Rust.
Overall, the Teensy 3.1/3.2 family wasn't great for developing Rust, as they don't have debugger (SWD, similar to JTAG) lines available, meaning you have to use the serial bootloader, and rely on a serial port for all debugging. I believe the newer version of the board expose SWD lines now, so it's not a problem.
Let me know if you have any questions :)
Definitely check out the embedded WG[1], and the new Rust homepage[2]
[1]: https://github.com/rust-embedded/wg [2]: http://beta.rust-lang.org/what/embedded
Originally, our first push was to get Cortex M bare metal microcontrollers as a "Tier 1" stable target for the 2018 edition of Rust.
Over the last couple months, we've been expanding, and have subteams for a bunch of different topics, including chip support, drivers, documentation, tooling, etc. We're mostly focused on helping other people who are getting started with embedded rust, as well as give feedback to the compiler teams, etc.
It would be interesting to hear more about your porting attempt, we also have a blog - https://rust-embedded.github.io/blog/ - if you'd like to share it as a blog post.
As Steve mentioned, https://github.com/rust-embedded/wg is our main coordination repo, and has links to most of the stuff we're actively working on.
Happy to answer any questions about the talk, or embedded systems in Rust in general.
I played empire (in the classic text mode) together with my dad probably more than 20 years ago.
Thank you for the game (I have lots of fond memories playing this with my dad), and for reminding me what the name was!
I originally included the output of `size` for each step, but I thought it made the text output too large. However in this case, the actual size of binary on "disk" is important, as we were trying to fit this binary on a small embedded linux device, so if we had shipped all of that debuginfo, it would have taken up useful space on the device (which has a total storage size of 8MB).
Regarding UPX, yup, not Rust specific at all, but still relevant when talking about producing tiny binaries.
Re: the allocator, steveklabnik wrote a good response, though I would add that just because something isn't written in Rust, doesn't mean it can't still be well tested, performant code. Why rewrite it in Rust if you don't have to? :)
Anyway thanks for reading and thanks for the feedback!
I really like the idea of this! I have a couple questions:
* Do you support any sort of formatting for the contents of the book? e.g. Markdown, LateX, ? Or is it all "subject": $email_title, "text": $email_body?
* Do you have any estimate on how much text fits in a 5x8 book? Does your printing service scale the width of the book based on contents? Aka, if I wrote "walked dog, ate food", every day, would I get a pamphlet? Is there some kind of upper limit?
* Do I have to buy all my cheat days up front? It seems like you could charge "absolutions", maybe even at the end, maybe something like $0.50 for non-prepaid days? It might help people throw good money after bad :)
Thanks for sharing!
Not Steve here, but I was wondering if you were being sarcastic here:
> Make rust playful.
Why am I asking if you're being sarcastic?
> Make a game framework
> Make it build on a mobile device
https://www.bignerdranch.com/blog/building-an-ios-app-in-rus...
> Make it build on a Pi... without diarrhea
curl https://sh.rustup.rs -sSf | sh
> Make it build for the Arduino(An ARM based Arduino, AVR [which powers the original Arduinos] support is being worked on now)
https://github.com/jamesmunns/teensy3-rs
> Cross compile it to Javascript
From wikipedia: https://en.wikipedia.org/wiki/Circadian_rhythm