sunshowers

Thanks Andrew! Honestly I learned so much about what makes unsafe Rust so hard from building iddqd.

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)

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.

Read the fine article?

> While the tax seems large, experts say the city’s antiquated assessment and valuation system dramatically undervalues properties, reducing the burden. City valuations can often be 10% or less of the true market value, they said.

Read the fine article?

> While the tax seems large, experts say the city’s antiquated assessment and valuation system dramatically undervalues properties, reducing the burden. City valuations can often be 10% or less of the true market value, they said.

In my experience, LLMs benefit greatly from the existence of sum types and exhaustive pattern matching.

Personally I think we should declare that b and strong mean the same thing, and that i and em mean the same thing. As the other commenter points out, there's no real semantic difference between "bring attention to" and "emphasize".

The Oakland CA DMV, which is the one I live closest to, is quite nice. I've never had a bad time there.

So then what's the point of making this distinction? I would like to see surveys of how many people actually author content in forms that differentiate between b and strong.

Trump has -20% to -25% net approval depending on the poll, and his approval rating on immigration is -10 to -15%. Clearly people do not like any of this in practice even though they might have liked it in theory.

Is the goal here to be the same as others or to be better than others? The US immigration system is far from great at the best of times, but it's becoming worse over time.

I write most of my content in markdown or asciidoc and I don't pay attention to whether it's b or strong :)

Bleh. <b> is apparently now bring attention to. As if.

One might argue that the composition of higher abstractions is the next token predicted after "here is a higher abstraction:"

There are two ways to express such ratios, and both are equally valid. (Though "x" is usually reserved for "40x" and "%" for "97.5%".)

Olivia uses she/her, and I believe she is now retired :)

I owe her and the Mercurial community a great debt. The community taught me how to think like an engineer building infrastructure and the importance of backwards compatibility, something I've tried to carry forward in tools like cargo-nextest.

Yes? "Different cultures" doesn't just mean different countries; there are many cultures within infosec.

I don't think mailing stacks of patches is that different? As someone who built this stuff it was pretty obvious to me that web-based patch stack management was a relatively small evolution over mailing lists. Tools like patchwork bridged the gap initially, and we were quite familiar with them.

To my knowledge, stacked diffs were first done in the Linux kernel as stacks of patches sent over email. From there they spread to Google and Facebook. (Source: I worked on Facebook's source control team from 2012-2018 and did a lot of work to enable stacked diffs there.)

If it doesn't work on Windows, it is not a full replacement.

Yep! Here's an experience report: https://github.com/hegeldev/hegel-rust/issues/148

A big issue with the macOS style I'd that there isn't a modifier key free for the user to build their own shortcuts around. The Win/Super key is a very good place to hang custom shortcuts off of on Windows and Linux.

A fun recent experience I had with Claude was I asked it to write a model for PBTs against a complex SUT, and it duplicated the SUT algorithm in the model — not helpful! I had to explicitly prompt it to write the model algorithm in a completely different style.

Thank you! I have some particularly annoying proptest-based tests that I'll try porting over to Hegel soon. (Thanks for writing the Claude skill to do this.)

Hi David, congratulations on the release! I'm excited to play around with Hypothesis's bitstream-based shrinking. As you're aware, prop_flat_map is a pain to deal with, and I'd love to replace some of my proptest-based tests with Hegel.

I spent a little time looking at Hegel last week and it wasn't quite clear to me how I'd go about having something like a canonical generator for a type (similar to proptest's Arbitrary). I've found that to be very helpful while generating large structures to test something like serialization roundtripping against — in particular, the test-strategy library has derive macros that work very well for business logic types with, say, 10-15 enum variants each of which may have 0-10 subfields. I'm curious if that is supported today, or if you have plans to support this kind of composition in the future.

edit: oh I completely missed the macro to derive DefaultGenerator! Whoops

My understanding is that that is a maximalist position for the avoidance of risk, and is sufficient but probably not necessary.

History search, like in shells. My most used TUI shortcut!

A very important thing about constraints is that they also liberate. TUIs automatically work over ssh, can be suspended with ctrl-z and such, and the keyboard focus has resulted in helpful conventions like ctrl-R that tend to not be as prominent in GUIs.

I'm not a professional, but to me it's clear that whether i and -i are "the same" or "different" is actually quite important.