Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sunshowers
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
31.
▲
by
sunshowers
3mo ago
From what I can tell, a big part of the problem in Europe is that people seeking asylum are prohibited from making a living (due to widespread belief in the lump of labor fallacy) and so have to be dependent on welfare.
32.
▲
by
sunshowers
3mo ago
The benchmarks are against non-doctest cargo test runs. (But you should measure against your own project, of course!) Unfortunately Cargo doesn't provide enough information for nextest to run doctests reliably with.
33.
▲
by
sunshowers
3mo ago
I think in practice you're right that GitHub Actions' caching slowness can end up dominating performance. I don't have any great tips other than to measure.
34.
▲
by
sunshowers
3mo ago
> Can you run tests serially in the (horrible) case when tests need to build on one another? Yes: https://nexte.st/docs/configuration/test-groups/ (edit: though tests that build on each other is a bit hard
35.
▲
by
sunshowers
3mo ago
Thanks! BTW you might enjoy setting CARGO_TERM_COLOR=always in your environment :) dtolnay/rust-toolchain does this automatically but it looks like you aren't using that action.
36.
▲
by
sunshowers
3mo ago
Oh gosh, were we to be so lucky :) just aiming to solve problems my coworkers and users see, and doing it with care, is all.
37.
▲
by
sunshowers
3mo ago
The How it works [1] and Why process-per-test? [2] pages should answer your questions. [1] https://nexte.st/docs/design/how-it-works/ [2] https://nexte.st/docs/design/why-process
38.
▲
by
sunshowers
3mo ago
Yeah that was indeed the inspiration (though I'm pretty sure it predates Kubernetes!) but the juxtaposition with "terminate" is unfortunate.
39.
▲
by
sunshowers
3mo ago
That's fair! I'll find a way to rephrase it. edit: Updated to "Detect and handle slow tests". Thanks again!
40.
▲
by
sunshowers
3mo ago
That is indeed the pun =)
41.
▲
by
sunshowers
3mo ago
Thanks for posting about this! I'm the main author of nextest, and it represents my best foot forward for how Rust testing should be done. Happy to answer questions though I might be a bit intermittent.
42.
▲
by
sunshowers
4mo ago
I'm sure you're aware there's a huge amount of computation that isn't matrix multiplication :)
43.
▲
by
sunshowers
4mo ago
My successful application took around 12 hours of writing and editing across 3 days, though I was lucky that most of my portfolio was already open source or otherwise public. Some people spend more, some spend less. It is worth keeping in m
44.
▲
by
sunshowers
4mo ago
We have a number of TLA+ models at Oxide. Here's one: https://github.com/oxidecomputer/omicron/blob/8b0886dbd02229...
45.
▲
by
sunshowers
4mo ago
Updated https://oxide.computer/blog/iddqd-unsafe#what-about-formal-m... with some notes.
46.
▲
by
sunshowers
4mo ago
Mostly chatted with some people and figured it out with their help.
47.
▲
by
sunshowers
4mo ago
Rust is a beautiful language. Gorgeous.
48.
▲
by
sunshowers
4mo ago
I'm a huge fan of Rust! I like to think my writing makes the Rust community better more than it annoys people :)
49.
▲
by
sunshowers
4mo ago
If you are interested in a more nuanced take on what makes unsafe Rust both valuable and difficult, check out my blog post on the Oxide blog: https://oxide.computer/blog/iddqd-unsafe I directly tackle the concerns you
50.
▲
by
sunshowers
4mo ago
I look at people saying things like "Rust has a miserable DX" and I wonder whether I live on a different planet from them.
51.
▲
by
sunshowers
4mo ago
A one-shot process is easier to build and reason about than an event-driven server (speaking as someone who has written plenty of both).
52.
▲
by
sunshowers
4mo ago
The problem is that threads are not fault boundaries but processes are. So they're not interchangeable when you care about resilience and misbehaving code.
53.
▲
by
sunshowers
4mo ago
The secure/double slip knot that's linked in the story. I practiced it a few times (making sure the knots are in opposite directions took a bit of retraining muscle memory) and can tie it by heart now.
54.
▲
by
sunshowers
4mo ago
Thank you for the link! Just donated. That site changed my life in a small but persistent way — my shoelaces haven't come undone in more than a decade now.
55.
▲
by
sunshowers
4mo ago
Elliptic curves over reals and the complex numbers had some physical/scientific meaning, but elliptic curves over finite fields had none before cryptography.
56.
▲
by
sunshowers
4mo ago
Since iddqd works on structured data, the model-based tests (while not being coverage-guided) do a lot of the kinds of things fuzzing would do against an algorithm which accepted unstructured data. In principle the bitstream from which stru
57.
▲
by
sunshowers
4mo ago
At this point the subsidized rates are only available with individual plans. In principle your workplace can pay for an individual plan for you, but for compliance reasons that is likely only feasible at smaller places that are primarily op
58.
▲
by
sunshowers
4mo ago
Thanks Andrew! Honestly I learned so much about what makes unsafe Rust so hard from building iddqd.
59.
▲
by
sunshowers
5mo ago
I agree that owning an expensive house where you have negative equity is not wealthy (at least based on that data point itself; maybe you have a 401k or something else that makes you wealthy)
60.
▲
by
sunshowers
5mo ago
In what world is 1 million US not wealthy? Have tech salaries distorted people's opinions that much? Owning a house where your equity in it is over a million is absolutely wealthy.
More ›