Viewing profile — sunshowers

I mean, really no one is fully independent — we are all dependent on each other for the necessities of life. But in this context "independent" means "not a subsidiary of another co…

Right -- customers don't have to port their stuff to a new platform or arch or anything. It's just normal x86_64 Linux/Windows VMs, or Terraform if they're so inclined.

We are trying to build a sustainable long-term business! It's just that you need enormous amounts of money to get there when shipping this large a product. The idea behind VC fundi…

It's not actually secret — it's open source! We talk openly about our architecture. Bryan has a good take on the incentive structures holding back commodity hardware vendors: https…

That's wonderful! Good luck.

Indeed, and I happened to have been part of the creation story for one of them :) https://lobste.rs/s/ghdv6w/i_see_future_jj#c_nx6flj (not otherwise affiliated, though)

GitHub has a chance to get a generation of developers on to better coding practices. LLMs make it more feasible than ever to maintain high-quality patch series/stacked diffs — they…

I use `spr` which translates a local rebase + amend workflow into a GH-friendly new-commit + merge on the remote (which is then squashed). They are kind of equivalent from a 30k fo…

The seeming lack of engagement with prior art is so frustrating.

You don't have to expose change IDs in the UI other than as a secondary thing! The current integer index would work just fine.

That is nowhere close to the experience Gerrit and Phabricator have, where you can diff two arbitrary versions in history. Comments on previous versions also get lost along the way…

I apologize for being somewhat direct but what prior art did you engage with? Why are you making people create a branch for each change in a stack? Why do developers have to create…

Like all things in life, there is a balance :) I didn't remove the cattle vs pets analogy but I did replace "terminate" with "handle".

Look, you can either let people make a living and manage their own lives while contributing to society, or you can not let them make a living and ensure they're housed and fed. You…

Nextest does run tests in lexicographic (binary, test name) order by default, so first executions tend to be staggered. Unfortunately this is a known problem that is much larger th…

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) …

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 nex…

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.

> 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…

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.

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.

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-p…

Yeah that was indeed the inspiration (though I'm pretty sure it predates Kubernetes!) but the juxtaposition with "terminate" is unfortunate.

That's fair! I'll find a way to rephrase it. edit: Updated to "Detect and handle slow tests". Thanks again!

That is indeed the pun =)