erickt

17 ms·

1.
by erickt 4y ago
I also work on Fuchsia’s Software delivery team. For some more detail on how we secure downloading components, we implement a concept called verified execution [1]. We establish a chain of trust from: * a hardware key (on hardware that supp
2.
by erickt 5y ago
ABI and API backwards compatibility is written up here: https://fuchsia.dev/fuchsia-src/development/languages/fidl/g...
3.
by erickt 5y ago
I believe the first major funding by the Rust Foundation was hiring Ferrous to help develop and maintain crates.io: https://foundation.rust-lang.org/posts/2021-10-18-crates-io-...
4.
by erickt 5y ago
I’d go further and say it’s not possible to fully implement async/await without compiler help. I got really far with stateful, back in 2016 [1]. Stateful was an attempt to write a coroutine library in a proc macro, which generated stat
5.
by erickt 6y ago
The account issues have apparently been resolved, and Terraria port to Stadia has been uncanceled: https://forums.terraria.org/index.php?threads/terraria-state... Disclaimer: I work at Google, but don’t work anywhere n
6.
by erickt 6y ago
Could (2017) be added to the title? Since then, Daniel has since rethought this post and is now writing a Rust backend for curl: https://daniel.haxx.se/blog/2020/10/09/rust-in-curl-with-hyp...
7.
In-toto: A framework to secure the integrity of software supply chains(in-toto.io)
4 points by erickt 6y ago|0 comments
8.
by erickt 6y ago
This is great news! I'm glad Servo found a place to land. Are you planning on sticking with the MPL-2.0 license, or are you also considering relicensing as well?
9.
by erickt 6y ago
> Closed-world ("sealed") traits. Rust's rules against private types in the public API are good civilization but they make it difficult to define pseudo-private traits like Mount that I want users to name but not implement
10.
Mutexes are faster than Spinlocks(matklad.github.io)
373 points by erickt 7y ago|145 comments
11.
by erickt 7y ago
Original author of serde here. I call it sir-dee, but the current maintainer, dtolnay, calls it sear-day. But we really don't care how people pronounce it. It's really more of a neither / potato thing: https://www.
12.
by erickt 9y ago
The official rust book [1] is a great place to start. So are the exercism tutorials [2] [1] https://doc.rust-lang.org/book/ [2] http://exercism.io/languages/rust/about
13.
by erickt 9y ago
Drat, that must be the jekyll syntax highlighter. It might be easier then reading it off of github if you or anyone else has problems with reading the post: https://github.com/rust-community/blog.community.rs/blob&
14.
by erickt 9y ago
Organizer here! Aidan actually submitted two entries. This particular entry that exploited this unsoundness bug wasn't actually the winner, even though it was great (horrible?). We weren't sure if the underhandedness would survive
15.
by erickt 9y ago
Yeah, there's progress on 8-bit and 16-bit support. We're tracking our work on improving Rust for embedded systems in this roadmap issue [1], with details in this RFC repo [2]. As part of that, we have preliminary support for the
16.
by erickt 9y ago
Good idea. I noted that for next year's survey [1]. One of our big initiatives this year is working on our ergonomics [2]. I'm not sure if we can ever get as approachable as Python, but we've been working hard on trying to ma
17.
by erickt 9y ago
Rust Core team member here. Our code of conduct [1] has been the fundamental cornerstone of our project and community since the beginning. Every large institution ends up having to choose explicitly or implicitly how they deal with conflict
18.
by erickt 9y ago
Core/Community team that helped design the survey here. We actually did ask about this, but unfortunately it's quite time consuming to process through all the free text entry like this one. Some of the popular things people want f
19.
by erickt 9y ago
Rust Core/Community Team member here, who helped design the survey. You got it. We asked this question to check whether or not we're succeeding at maintaining our backwards compatibility. While we have great visibility on if we&#x
20.
by erickt 9y ago
Servo is still considered a research project, but one of the benefits of sharing WebRender, Stylo, etc between Servo and Firefox is that it is really helping to productionize those systems. That then will make it easier to turn it into a re
21.
by erickt 9y ago
> Kubernetes "secrets" aren't actually...well...secret. They're stored unencrypted in etcd with no ACLs. You must go outside the Kubernetes system to do this. They are in progress towards encrypting at rest the etcd d
22.
by erickt 9y ago
FYI, rkt was created (and I believe still predominantly maintained) by CoreOS: https://coreos.com/rkt
23.
by erickt 9y ago
One of the most important tools when writing unsafe rust is compiletest [1]. It's a tool extracted from the compiler project that lets you write tests that are supposed to fail compilation. Since safe abstractions rely on the type syst
24.
Online reconstruction of structural information from datacenter logs(blog.acolyer.org)
2 points by erickt 9y ago|0 comments
25.
by erickt 9y ago
Hello! Rust core and community team member here. If you (or anyone else) are serious about trying to fund development of Tokio, please send us an email at community-team@rust-lang.org and we would happily connect you to people working on th
26.
by erickt 9y ago
I think that was one of the proposed variations, but we ended up picking the shorter .expect to cut down on repetition. We expected (ha) that this function would be used in these one-offs, so we wanted something more efficient.
27.
by erickt 9y ago
That is a good point. I'm going to have to start being more positive in my expectations :)
28.
by erickt 9y ago
If I recall correctly we just couldn't come up with a great name for it. To me "expect" is a positive action, but the argument is about it failing to meet the expectation. Semantically I like `thing.unwrap_or(|| panic!("
29.
by erickt 9y ago
Hello Justin Turpin! Sorry to hear your struggles with rust. It's always going to be a bit more verbose using rust than Python due to type information, but I think there are some things we could do to simplify your code. Would you be c
30.
by erickt 9y ago
Hello everyone! Rust Community team member here. We would greatly appreciate a moment of your time to help us understand how we did over the past year, and how we can improve over the next year. We'd love any input from people both alr

More ›