palmtree3000

That's a different post.

Withholding isn't relevant here. Non refundable means it can't cause the government to net pay you money: that is to say, it can't make your refund larger than your withholding.

since we are not solving the problem at hand in a good way, we decided to solve it in a worse way

It's a different "we". Rephrased:

since Houston's government is not solving the problem at hand in a good way, Waymo decided to solve it in a worse way

Silicone is not rigid, which is sometimes a problem.

They have this for babies! It comes in powder and puff form. It's to prevent babies from developing allergies.

Sure it is! If we were trying to compress an archive of orbital data, one way to do it would be "initial positions + periodic error correction". If you have the new planet, your errors will be smaller and can be represented in less space at the same precision.

Firefox can screenshot the entire page: https://support.mozilla.org/en-US/kb/take-screenshots-firefo...

Don't forget CS2: Episode 1!

Isn't this chapter 11 bankruptcy?

Wait, can you link to that?

I believe inkscape has this: http://tavmjong.free.fr/INKSCAPE/MANUAL/html/Paths-LivePathE...

Re: auto generated code: it saves ci time which is a pretty huge benefit. You still need to regenerate the code to make sure it's up to date, but you can do that in parallel with tests that rely on that code.

High school is a bit under a third of school years in the US, so that's a high school of about 3000 (which is how big my high school was, for example).

You need a heat difference, not just heat, to generate electricity.

Now my sibling comment links to a paper where they say they can find heat differences in the body that are sufficient for their needs, so this is still a possibility! But it does mean you need to be somewhere with a heat gradient: the paper mentions just under the skin.

Sure, but you can make it as progressive as you want by redistributing the tax income back to people.

I think odds ratio ( p/(1-p) ) is the thing I'd use here. It gives the right limiting behavior (at p ~= 0, doubling p is twice as good, and at p~=1, halving 1-p is twice as good) and it's the natural way to express Bayes rule, meaning you can say "I'm twice as sure (in odds ratio terms) based on this evidence" and have that be solely a property of the update, not the prior.

I came to rust from the other direction, as it were: from Haskell.

There are a lot of similarities! The type systems are similar, with some name changes (sum types -> enums, typeclasses -> traits). Pattern matching is basically the same. Haskell uses (lazy) lists mostly the same way rust uses iterators. Ownership is new, but imposes some of the same requirements that immutability does (no cycles without shenanigans[0]). Rust requires that values are aliasable XOR mutable: Haskell does too (they're always aliasable and never mutable).

[0] https://wiki.haskell.org/Tying_the_Knot

Gravitational lensing. From the description[0]:

Other features include the prominent arcs in this field. The powerful gravitational field of a galaxy cluster can bend the light rays from more distant galaxies behind it, just as a magnifying glass bends and warps images. Stars are also captured with prominent diffraction spikes, as they appear brighter at shorter wavelengths.

[0] https://webbtelescope.org/contents/news-releases/2022/news-2...

I mean, these are all valid criticisms of the swimming experience, it just sounds silly because you can't edit swimming.

I realize this is a joke, but it isn't! Play a video of a ball flying up and then back down again and it'll be the same forward or backwards (up to air friction anyway).

Do you think there's any level of child abuse that shouldn't be unconditionally be forgiven as part of growing up?

I don't think Will's experience supports that. It's not that he gave some consent that, looking back on it, wasn't valid. Instead, he repeatedly and explicitly did not consent, and was ignored.

I'm not sure why choice of programming language is such a heated topic.

I think there are two reasons.

First, languages live or die by their ecosystems. If you love a language, it's very much in your interest for other people to use it, so they write code that you can use.

Second, most programming happens at work. Most people don't get to choose what programming language they write at work: they're locked into whatever choice somebody else made. The more popular your language is, the more likely that choice is to be made in your favor (or alternatively, the easier it'll be to find a job where that choice has been made in your favor). If I want to write Idris at work, well, tough luck.

Both of these are largely zero-sum, which makes things worse. It's not 100% zero-sum, in that if you manage to light a passion for <language> in somebody they might write code (in that language) that might not have been written at all. But mostly language evangelism won't change the total number of programming hours per year (or the number of available programming jobs), so all that's left is to fight over who gets how much.

So if you care a lot about which programming language you write, I don't think it's odd to come at it from combative angle: it's a fight! Some will lose and some will win, so you better try and be one of the winners.

"Incorrect" is way too strong here.

I agree that a reference frame that has about the same velocity as the stuff you care about is in some sense privileged. But the fact that we haven't seen the merger happen yet means that it's outside our light cone, which means there exists a reference frame where the merger hasn't happened yet.

that is to say, t_{this_coversation} < t_{merger}, in that frame.

You indeed don't have to pay long term capital gains tax, although you do have to pay short term capital gains tax.

Json diffing.

I haven't found any implementations I'd consider good. The problem as I see it is that there are tree based algorithms like https://webspace.science.uu.nl/~swier004/publications/2019-i... and array based algorithms like, well, text diffing, but nothing good that does both. The tree based approach struggles because there's no obvious way to choose the "good" tree encoding of an array.

I've currently settled on flattening into an array, containing things like String(...) or ArrayStart, and using an array based diffing algorithm on those, but it seems like one could do better.

You can make a consumption tax progressive! You'd probably want to make it a bit more progressive than the current income tax brackets, to cancel out the effect you're describing.

Re: implementation: make putting money into a bank account tax deductible and pulling money out taxable, then continue to use the existing income tax system. Any money you earn that you don't spend is a tax write-off, any money you spend that you didn't earn this year is something you have to pay more taxes on.

Honda fit? https://automobiles.honda.com/tools/build-and-price-trims?mo... "Starting at $16,190"

Apparently [1] it returns Option<Element>.

[1] https://rustwasm.github.io/wasm-bindgen/api/web_sys/struct.D...

I was briefly very excited when I read that article, actually. But as devit points out in a sibling comment, that technique is only relevant to cases where you're adding more than 2 numbers.

Multiplication initially seemed like a very promising use case, since it's basically repeated addition. But I'm not super optimistic about that, because I think it's dominated by the alternate optimization of noticing that the product of two 64 bit numbers cannot saturate the high 64 bits of the resulting 128 bit number, which causes carries to be bounded [1].

[1] https://github.com/rocurley/bignum/blob/b45448a156fb9100ab06...