alilleybrinker

6 ms·

1.
by alilleybrinker 6d ago
With these dimensions of design variance defined, you could also make a closeness measure in 9-dimensional space and identify the most or least similar combos. Also a great teaching tool, if someone knows one async system, to be able to sho
2.
by alilleybrinker 1mo ago
Product-market fit. Based on prior Oxide announcements, they've been clear the raising is in large part about building out manufacturing to meet customer demand. In venture capital investing, once you've found a winner (a company
3.
by alilleybrinker 3mo ago
It’s in the book. That’s the entire point of the book.
4.
by alilleybrinker 4mo ago
The section on how to do software assurance of unsafe code in Rust is excellent. A lot of prior guidance I've seen tends to stop at the level of running Miri, but (as the article says) there are things Miri won't catch. The model-
5.
by alilleybrinker 6mo ago
Did you read the article? The author makes exactly that point.
6.
by alilleybrinker 7mo ago
Wired should retract this homophobic article. It takes an issue of people in power abusing that power, and ties it to their sexuality, as if the men abuse their power because they’re gay, or as if straight men never do similarly. Identifyin
7.
Move over Gas Town, Claude Has First-Party Agent Orchestration(alilleybrinker.com)
1 points by alilleybrinker 7mo ago|0 comments
8.
by alilleybrinker 8mo ago
In situations like this I appreciate that Rust has a culture of semantic precision [1] and while this kind of API-clarification is painful in the short-term, I think it will be worth it for Linux. [1]: https://www.alilleybrinker.
9.
Gas Town Decoded(alilleybrinker.com)
219 points by alilleybrinker 8mo ago|234 comments
10.
by alilleybrinker 1y ago
For the disjoint field issues raised, it’s not that the borrow checker can’t “reason across functions,” it’s that the field borrows are done through getter functions which themselves borrow the whole struct mutably. This could be avoided by
11.
by alilleybrinker 1y ago
There's also the Common Weakness Enumeration (CWE), a long-running taxonomy of software weaknesses (meaning types of bugs). https://cwe.mitre.org/
12.
Open Source Software and Corporate Influence(alilleybrinker.com)
4 points by alilleybrinker 2y ago|0 comments
13.
by alilleybrinker 2y ago
The project maintainers had to both: 1) Decide to use the highly risky `pull_request_target` Actions trigger instead of the much safer `pull_request` trigger, 2) include in their Actions a script, executing in an environment with write acce
14.
by alilleybrinker 2y ago
The repository maintainers are running actions for PRs with the `pull_request_target` trigger, which gives full access to target repository secrets with write permissions. It's very explicitly documented as dangerous to do this. To mit
15.
by alilleybrinker 2y ago
There’s likely some amount of code which would not be rewritten into Rust but which would be rewritten into safe C++. Migrating to a whole new language is a much bigger lift than updating the compiler you’re already using and then modifying
16.
by alilleybrinker 2y ago
Alternatively, Rust's cell types are proof that you usually don't need mutable aliasing, and you can have it at hand when you need it while reaping the benefits of stronger static guarantees without it most of the time.
17.
by alilleybrinker 2y ago
Not everything will be rewritten in Rust. I've broken down the arguments for why this is, and why it's a good thing, elsewhere [1]. Google's recent analysis on their own experiences transitioning toward memory safety provide
18.
by alilleybrinker 2y ago
The article makes the particularly good point that you generally can’t effectively add new inferences without constraining optionality in code somehow. Put another way, you can’t draw new conclusions without new available assumptions. In Se
19.
by alilleybrinker 2y ago
It ought to be easier to get a blank slate of a small device with some compute power and a screen, like the Kindle here, without having to jailbreak something.
20.
by alilleybrinker 2y ago
Nice to see they identified Rust as a common language across many of the categories they surveyed! They specifically call out tooling, even for other languages, being written in Rust. As someone who myself builds a lot of CLIs in Rust, I th
21.
by alilleybrinker 2y ago
Here’s an article [1] quoting Walgreens’ CFO who, on an earnings call in early 2023, offered that Walgreens had in prior quarters likely overblown the level of shrink they were experiencing and expected to experience (“shrink” is the indust
22.
by alilleybrinker 2y ago
Right. A huge part of the value proposition of enterprise kernels is the stability, which you pay a cost for in the form of backporting and maintenance. That’s the thing that makes it valuable as a product! It really can’t be the policy of
23.
by alilleybrinker 2y ago
Greg KH's comment about not letting yourself be limited today by the needs of commercial users of old kernels is a good one [1]. That would be a tail wagging the dog situation, where newer APIs can't improve beyond the support tha
24.
by alilleybrinker 2y ago
Mickos is quoted: "The power of open source is not that we agree and get stuff done; it is that we disagree and get stuff done. That’s the true power when you have a governance model that allows people who have nothing in common to pro
25.
by alilleybrinker 2y ago
I definitely agree on the mission alignment and strong ethical orientation of non-profit work being a big motivator. I've worked for MITRE, a non-profit that runs Federally Funded Research & Development Centers (you might remember
26.
by alilleybrinker 2y ago
Very interested in exploring how this will compare to Diesel [1] and SeaORM [2], the other two options in this space today. Joshua Mo at Shuttle did a comparison between Diesel and SeaORM in January of this year that was really interesting
27.
by alilleybrinker 2y ago
In part two, the author explains trait objects in a way that is, I think, a little misleading. They're right that trait objects are dynamically sized types, which means they can't be passed by value to functions, but wrong that th
28.
by alilleybrinker 2y ago
Code patterns are social! What is strange to one is normal to another. The kind of pattern used here with the `||` might seem weird to some JavaScript developers, but it's pretty normal in shell scripts, and it's pretty normal in
29.
by alilleybrinker 2y ago
There is no such thing as universally self-documenting code, because self-documentation relies on an assumption of an audience — what that audience knows, what patterns are comfortable for them — that does not exist in general. Self-documen
30.
by alilleybrinker 2y ago
You are mistaken. The work described here is based on this paper, currently published as a preprint: https://www.medrxiv.org/content/10.1101/2024.08.15.24312078v... This preprint is the first link in the article.

More ›