Ok, there is a LOT of interest on the topic in the @rustlang community 
Let's do it!
It'll take a while, but worth it.
I put together a small announcement and a mailing list if you'd like to be notified when the first episode comes out https://www.lpalmieri.com/posts/2020-05-10-announcement-zero-to-production-in-rust/ …
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I’d love to see also a discussion of why Rust is a good fit for building an API. I’m also curious to see how ergonomic writing APIs and what are the pain points. E.g. I expect to see many macros to help with ergonomics. Do they cause slow build time?
-
In a nutshell, I'd say that Rust is an extremely good fit for domain-rich applications - the type system is invaluable when it comes to domain modelling. At the same time, it gives you very predictable performance out of the box (no GC ma!) with low resource usage.
- 4 more replies
New conversation -
-
-
does "from scratch" mean "I'm gonna use 50 crates"? Or like actually from scratch?
-
Not 50, but probably a good handful of them. Re-implementing every component is out of the scope of the project - we will be using what is available in the ecosystem when possible, rolling our own where needed. Contributing upstream if indeed useful outside of the course itself.
- 3 more replies
New conversation -
-
-
I think it might be more interesting to talk about what Rust is good at it in the context of REST APIs first! By design it's more to get it doing useful things than Python/PHP/Node/etc but other aspects like correctness, performance and threading are quite unique.
-
I agree, but at the same time I prefer a "show don't tell" approach - I'll give you a peek of what it looks like to develop one, then you are free to decide if that is ergonomic/better/worse than your current go-to language or framework :)
- 3 more replies
New conversation -
-
-
You should do it! We use it in production for a year now, building a web service with graphql. We should push forward the web stack written in
#Rust because it's awesome. -
Not much experience with GraphQL: how has your mileage been so far?
End of conversation
New conversation -
-
-
I’m down for that, but is a framework a necessary thing? Go has a strong http stdlib and knowing about it isn’t useless knowledge. Does the rust stdlib facilitate a baseline and can you then show how these frameworks extend that?
-
Rust standard library has a very different approach to Go's standard library: it's not battery included. No async runtime, no HTTP support, no HTTP client. Everything is defined by crates in the ecosystem.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Writing about stuff to learn how it works, mostly in Rust.
Lead Engineer at