DreadY2K

> If it is just a land tax, however, you can game it by building as much as possible on it

That's not gaming it, that's the tax working as intended. We need more housing, so if that gets people to build more of it, that's a win.

How long until support gets added for repos with merge queues? I'd love to use this at $WORK and so would my coworkers, but we can't turn off the merge queue so we can't use stacked PRs until they can mix.

Not GP but I feel like there's a continual process of the stdlib adding some new functionality to make one such crate redundant (e.g. is-terminal in 1.70), but it isn't done yet.

I noticed my 13 thermally handles being on a soft surface (like a bed or a couch) very poorly, it gets quite warm to the touch and runs the fans hard even at rest. Does the improved thermals of the 13 pro also help this case?

Similar story here. Mine is 3 years old, and the battery is about 80% of its original capacity and the touchpad occasionally drops clicks, but otherwise it's still working great! Also the charging cable frayed, but I have plenty of those cables around.

> how, after 6 months' travel in deep space, will they accomplish anything at a Mars base, even mere survival?

I expect the answer is spin gravity. Have a long cable with a counterweight on the other end, spin it at some rate. We would need some studying about the exact impacts (how hard is it to learn to start/stop compensating for Coriolis forces?), but it'd be much easier than full weightlessness.

> e.g. a family member or your boss can tell you who to vote for and force you to submit that vote.

Where i live, you can show up in-person on election day to override a mailed ballot, if you're in a situation like that.

> I’m only claiming that it’s memory safe and I am defining what that means with high precision

Do you have your definition of memory safety anywhere? Specifically one that's precise enough that if I observe a bug in a C program compiled via Fil-C, I can tell whether this is a Fil-C bug allowing (in your definition) memory unsafety (e.g. I'm pretty sure an out-of-bounds read would be memory unsafety), or if it's considered a non-memory-safety bug that Fil-C isn't trying to prevent (e.g. I'm pretty sure a program that doesn't check for symlinks before overwriting a path is something you're not trying to protect against). I tried skimming your website for such a definition and couldn't find this definition, sorry if I missed it.

I typically see memory safety discussed in the context of Rust, which considers any torn read to be memory-unsafe UB (even for types that don't involve pointers like `[u64; 2]`, such a data race is considered memory-unsafe UB!), but it sounds like you don't agree with that definition.

I don't have sources on hand, but my understanding is that there are a lot of people who come to CA without a good plan nor a social support network, become homeless, and then people misinterpret that situation as them coming here while homeless, which then gets misinterpreted as homeless people being intentionally shipped here.

Maybe this isn't the case for you, but a number of creators I watch have some videos that they only upload to Nebula. So it's worth it for me to see those videos I otherwise wouldn't ever get to see.

I got 48%, so no not everyone does.

Ah yes, because Signal is famously the app you use to be alone and not interact with anyone else

Will it be possible to upgrade my current framework laptop to the new 16" form factor? It feels like it should be a possible upgrade, but I haven't seen anything saying that it will be possible, so I'd like to confirm.

If you pick the DIY version, that is an option. I got mine with no OS preinstalled and no MS tax, and it was easy enough to install Manjaro.