sunshowers

7 ms·

91.
by sunshowers 9mo ago
Ah yes, the inevitable future where the only way we'll know to interact with the machine is through persuading a capricious LLM. We'll spend our days reciting litanies to the machine spirits like in 40k.
92.
by sunshowers 9mo ago
I talk to one of my doctors over Signal.
93.
by sunshowers 9mo ago
Language-specific package managers are a natural outgrowth of wanting portability across platforms.
94.
by sunshowers 10mo ago
?
95.
by sunshowers 10mo ago
You have to turn rerere on, though, right? I've never done that. I've also never worked with long-running branches — tend to strongly prefer integrating into main and using feature flags if necessary. Jujutsu doesn't have any
96.
by sunshowers 10mo ago
To be honest I've used rebase-heavy workflows for 15 years and never used rerere, so I can't comment on that (been a happy Jujutsu user for a few years — I've always wondered what the constituency for rerere is, and I'm
97.
by sunshowers 10mo ago
I have an early draft of a blog post about them :) as a source control expert who built both these systems and tooling on top of them for many years, I think they're the biggest and most fundamental reason rebases/linear history a
98.
by sunshowers 10mo ago
LLMs are pretty good at generating and maintaining error enums for you these days.
99.
by sunshowers 10mo ago
Do you know what criss-cross merges are and why they're bad?
100.
by sunshowers 10mo ago
> If you aren't instantiating a template, then it isn't used, so who cares if it has theoretical errors to be figured out later? This seems like a very strange argument to me. For a pleasant experience you generally want to rep
101.
by sunshowers 10mo ago
True but you lose out on much of the functionality of templates, right? Also you only get errors when instantiating concretely, rather than getting errors within the template definition.
102.
by sunshowers 10mo ago
Note that while C++ templates are more powerful than Rust generics at being able to express different patterns of code, Rust generics are better at producing useful error messages. To me, personally, good error messages are the most fundame
103.
by sunshowers 10mo ago
It depends. I've been working on a series of large, gnarly refactors at work, and the process has involved writing a (fairly long), hand-crafted spec/policy document. The big advantage of Opus has been that the spec is now machine
104.
by sunshowers 10mo ago
True!
105.
by sunshowers 10mo ago
You sound like my teacher in school, after my friend submitted an assignment so good my teacher thought he was cheating.
106.
by sunshowers 10mo ago
> Rust should have done exactly one thing and do that as good as possible: be a C replacement and do that while sticking as close as possible to the C syntax. The goal of Rust is to build reliable systems software like the kind I've
107.
by sunshowers 10mo ago
I do actually have this setup going with a Cable Matters adapter [1] + a custom firmware I found [2] and > chroma/RGB 4:4:4 + HDR + VRR/Freesync + 4k,120hz for their Linux PC on a TV works great now on my LG C4 TV with Bazzite&
108.
by sunshowers 10mo ago
JavaScript does not have a separation between & and &mut.
109.
by sunshowers 10mo ago
I didn't know about that incident before starting at Oxide, but if I'd known about it, it absolutely would have attracted me. I've written a large amount of technical content and not once in over a decade have I needed to u
110.
by sunshowers 10mo ago
I'm not sure about research, but I've used LLMs for a few things here at Oxide with (what I hope is) appropriate judgment. I'm currently trying out using Opus 4.5 to take care of a gnarly code reorganization that would take a
111.
by sunshowers 10mo ago
Jujutsu is not a Git frontend, it is an independent VCS that is compatible with Git. This is important because it has concepts and ideas of its own. It is used entirely independent of Git within Google.
112.
by sunshowers 11mo ago
Editions can definitely be made to alter standard library APIs in principle, thought the machinery for that probably needs to be developed a bit. But that's why I qualified my proposal with "if a breaking change is going to happen
113.
In defense of lock poisoning in Rust(sunshowers.io)
60 points by sunshowers 11mo ago|6 comments
114.
by sunshowers 11mo ago
No? Clearly outlining the pitfalls of a proposal is not a threat.
115.
by sunshowers 11mo ago
I have separate PCs for gaming and work. The former lives in the living room and the latter by my desk.
116.
by sunshowers 11mo ago
Acknowledging that panic safety is a real issue with data structures that mutex poisoning does not solve, I don't think we're going to agree on anything else here, unfortunately. We probably have entirely different experiences wri
117.
by sunshowers 11mo ago
If the issue is that everyone has to write an extra unwrap, then a good step would be to make lock panic automatically in the 2027 edition, and add a lock_or_poison method for the current behavior. But I think removing poisoning altogether
118.
by sunshowers 11mo ago
I understand what you mean, but you're saying has not been true for me in practice. Mutexes absolutely are used to uphold invariants in a way that &mut T is much less often. There's something to be said here about what I'
119.
by sunshowers 11mo ago
Correct yes, but my point was about cancellation in the middle of a critical section more generally.
120.
by sunshowers 11mo ago
(If unwinding goes away then, sure, mutex poisoning becomes moot.)

More ›