aero_code

Sounds like milliseconds since the page says

> Benchmarked on the Linux kernel's 1.48M commits, 96K files, our engine returns the first search results in under 20 ms.

I would love if everything on a computer were instant. One of the fastest programs I use is Sublime Merge for a Git UI. It opens and does everything so fast, and I love it. Since the first time I opened it, I haven't even opened the previous Git GUI I was using, even though I like both their UIs about the same. I had to buy Sublime Merge, compared to the free app I was using before it.

It's not just me who prefers everything as fast as possible, but true of people in general. Google measured that slowing down loading a search page by only 400ms caused people to do fewer searches. And the biggest reason I heard people say they switched to Chrome was that it was faster than other browsers (which was true for the first couple years after release).

I agree that Social Security is not plain welfare, but it has significant welfare components. Simplifying some, you get back something like 90% of the first $15,432 income per year but only 32% of income above that up to $92,988. (And above that, it's 15%.) Only getting 32% back of what you pay in so that the rest can be redistributed to others who made less could be considered partly welfare. Also, if you die too young, you don't get the money back, nor can you give it to your children. It's redistributed to other people. I'm not saying it's bad (I think it's probably good overall), but I can see how it's partly welfare.

I don't see a diagram on page 13, but I read a few pages around there. I don't see anything about it not applying to micro-enterprises. I see one diagram (PDF page 14/page num 11) that says a farmer selling "under own name or trademark to end user in another Member State" (without saying there's an exception for a micro-enterprise) means that the "Farmer is producer," which sounds like the opposite of what you said.

Ubuntu switched to the Paragon NTFS driver by default. When I upgraded to kernel 6.5 (I think) from Ubuntu, I started getting frequent kernel panics, like every day. Soon, I noticed that I couldn't even compile a Rust project on an NTFS partition because the compiler was getting random file system errors, and compiling was at high risk of causing a kernel panic. The NTFS driver in that kernel version is just totally broken. I switched to the FUSE NTFS-3G, and then I stopped getting panics and can compile stuff again no problem.

Looking at kernel commits, it looks like the driver may have been fixed since, but I'm scared to use it after it had such major brokenness in that version.

In addition to the sibling comment, even Minecraft server has an "online-mode" setting, and if it's set to false, it doesn't authenticate players. Whenever my family has played on LAN, we've never used any auth servers (which is clear because we don't give Minecraft any credentials). The setting only applies to LAN players, but that should be easy enough to work around with a VPN or something.

No, ICE did not kill those people. I looked through the latest six this year. Two were suicides (one suicide was of a man who had state charges against him for several crimes including child molestation), one was someone who had diabetes and refused to take insulin, and the others seem to have had other health issues. They got medical care many different times.

I think it is misleading to conflate murder with people dying of health issues in detention after medical care.

But sunscreen doesn't stop all damage to skin. I spent weekdays working inside on a computer, then sometimes spent summer weekends outside in the sun. I get sunburned easily, sometimes in like 10 minutes of direct sun. You wouldn't try to deny a light sunburn isn't skin damage? SPF 50 suncreen, blocking 98% of sun, extends the 10 minutes by 50x to 8.3 hours, but that is still not that great. I can still exceed that in two days. And I don't see why having light skin and wanting to spend the weekend outside would be unusual. Blocking 99% of UV and doubling the time over 98% would help quite a bit.

"it certainly will eventually" - I think even that is underselling how unlikely it is for Git 256-bit hashes to collide. I calculated (taking into account the birthday paradox), that even if 8 billion people on Earth each created a Git commit every second, that they would have to do that non-stop for 1,588,059,911 trillion years before there's a 50% chance that any of the two commits have the same hash. Our sun is predicted to only last 0.005 trillion years more.

√(2^256)×1.1774÷8000000000÷3600÷24÷365 = 1,588,059,910,945,875,138,261

UUIDs are more likely to collide but still basically impossible. You'd have to generate √(2^122)×1.1774 = 2714899559048203259 to have 50% chance of a collision. Just to store the UUIDs for that database would take 39,506,988 TB of space. If you aren't thinking about your database not fitting on millions of drives, don't think about UUID collisions.

The court decided the opposite--that APIs are copyrightable. However, the Supreme Court ruled that Google's usage was fair use, so I would agree that Google mostly won. The Supreme Court didn't consider whether APIs are copyrightable (the lower court ruled that) because Google would win regardless because it was fair use.

So I'm not sure it matters much whether APIs are copyrightable when what Google did was ruled fair use. I'd prefer if the courts ruled APIs weren't copyrightable, but I think it was still a good result because doing what Google did probably covers about any use case anyway.