jynelson

8 ms·

61.
by jynelson 3y ago
sure, i'm happy to chat more :) my email is on my website
62.
by jynelson 3y ago
i agree! i hadn't realized you were talking about people who weren't already team members. they're usually well-meaning, but it's true that some drain a lot of contributor time on things that aren't important. rust
63.
by jynelson 3y ago
two reasons: 1. writing in lowercase is freeing. it reminds me that grammatical rules are arbitrary, and by extension other rules. "you can just do things." 2. people who are pedantic about this when it's clearly intentional
64.
by jynelson 3y ago
rust definitely skews younger than average. i don't have statistics on hand, but almost all people i know working on the project are younger than 35, and a surprising number are 17-25
65.
by jynelson 3y ago
my shift key is there i just have conscientiously objected to it
66.
by jynelson 3y ago
i think this is partially true, but i hesitate to call people zombies. the vast majority of people in the rust project are competent and engaged. the problem is they have different priorities and collaboration is hard when everything is b
67.
by jynelson 3y ago
<3 wishing you well. good luck with your work. yes, there are lots of things you can do to get work done that don't involve you personally writing the code. i would like to write a post about that at some point but i have at least 3
68.
by jynelson 3y ago
this is mean-spirited. i am not talking about malfeasance in the project, i am talking about people who are trying their goddamn best and whose lives and jobs are at stake. what benefit do you think would come from announcing to the world &
69.
by jynelson 3y ago
i saw a fascinating blog post about this the other day https://www.zocalopublicsquare.org/2011/11/30/how-doctors-di...
70.
by jynelson 3y ago
this is a wonderful comment, thank you for writing it <3 i am trying to model these behaviors; this post was primarily intended for other people working in the project. i feel pretty strongly that this is a cultural issue moreso than an
71.
by jynelson 3y ago
i have some thoughts on it here: https://tech.lgbt/@jyn/111771280764615511 . i'm planning to make this the subject of my next blog post.
72.
by jynelson 3y ago
rust's CI is quite extensive actually; there's a talk on it here: https://www.pietroalbini.org/blog/shipping-a-compiler-every-... CI is good. more tests are good. but there's a limit to how much they can
73.
by jynelson 3y ago
i thought it was funny lol
74.
by jynelson 3y ago
it's not that simple. people form an emotional attachment to the work; they feel obligated to keep doing it. https://news.ycombinator.com/item?id=39027226
75.
by jynelson 4y ago
You can do that today, set CARGO_TARGET_DIR to an absolute path.
76.
by jynelson 4y ago
https://www.pingcap.com/blog/rust-compilation-model-calamity... is a good overview. In general it varies depending on the crate but we track the performance at https://perf.rust-lang.org/ - if you look
77.
by jynelson 4y ago
The original pointers `x` and `y` are not aliased. Only `x` and `y2` are aliases. Does the standard not allow you to pass any pointers which could be aliased based on arbitrary pointer arithmetic in the function body? That seems basically
78.
by jynelson 5y ago
It's not the maintainers - rustfmt has an official style guide it's not allowed to break without an RFC: https://github.com/rust-dev-tools/fmt-rfcs/blob/master/guide...
79.
by jynelson 5y ago
> "Parsing" is turning a stream of raw text or binary into some structured data types, i.e. a Rust type that your code can understand and use. This is a similar take to https://lexi-lambda.github.io/blog/20
80.
by jynelson 5y ago
> While it’s possible to audit the code of a crate on https://docs.rs on clicking on a [src] button, it turns that I couldn’t find a way to inspect build.rs files. Thus, combined with a malicious update, it’s the almost perfe
81.
by jynelson 5y ago
Spotify works fine offline, you just have to download the tracks ahead of time.
82.
by jynelson 5y ago
https://twitter.com/random_walker/status/1182635589604171776
83.
by jynelson 5y ago
The rust compiler itself can take as long as 2 hours on a modern laptop if you do a full stage 2 build. I don't think that's what the top poster was talking about though, it sounded like they had a rust toolchain already.
84.
by jynelson 6y ago
I'm helping work on the compile times :) https://github.com/microsoft/windows-rs/issues/420
85.
by jynelson 6y ago
This is such a depressing take. "I'm at work for 8 hours a day so it's ok if some time is wasted, there's plenty of it!"
86.
by jynelson 6y ago
> What I've been doing drops it to under thirty seconds in basically all cases. Is that for full builds or incremental? 30 seconds for a full build is reasonably fast (for rust, still feels slow IMO) but if that's incremental i
87.
by jynelson 6y ago
This ended up too long for a post on hacker news: https://gist.github.com/jyn514/5476c7b6122a3cb18825e1b883c18... tl;dr if you have a lot of dependencies more cores help a lot. If not, you hit diminishing returns; top
88.
by jynelson 6y ago
I find it interesting the article didn't mention compile times at all. Maybe since Oxide mostly works with embedded, they have few dependencies and their compile times aren't very bad? I know my primary complaint after working wit
89.
Intra-doc links close to stabilization – Inside Rust Blog(blog.rust-lang.org)
2 points by jynelson 6y ago|0 comments
90.
by jynelson 6y ago
You might be interested in https://github.com/holmgr/cargo-sweep

More ›