ahupp

What is the principle you’re using here?

I think the parent comment is saying “why did the agent produce this big, and why wants it caught”, which is a separate problem from what granular commits solve, of finding the bug in the first place.

Hilarious. When working on a virtual reality VOIP product, someone added a test mode that played back your own speech with a delay. It was like part of your brain shut off, was a surprisingly strong effect.

Do they need software? Presumably the volunteer firefighters 30 years ago didn’t have this and did fine. Plenty of volunteer organizations are built on Airtable or some spreadsheets.

IMO corporate income tax is the first that should be removed, with a corresponding shift to income taxes. Those can be as progressive as you want, have much lower compliance costs, and don’t distort behavior in the same way. Thought in practice I’m not sure how tax collection from foreign owners would work.

Can you quantify what you think that choice looks like?

Say you seized the entirety of Elon Musk’s assets: that could pay for a year and a half of the Dept of Transportation. Say you seized all the wealth (somehow) of the world’s 100 richest people. That’s 2 years of US non-discretionary spending (social security, Medicare and Medicaid). I often see comments that assume all problems could be solved by just taxing the rich more, but I just don’t think that’s true.

The Nordic countries pay for their social safety nets by taxing the middle class more heavily than we do in the US. If you want to change that, it’s less about capital vs labor, and more about your dentist vs labor (dentists be the classic example of jobs that earn high incomes without being “capital owners”).

With o3-mini-high (just the last paragraph):

civilization Mycenaean the of practices religious and economic, administrative the into insights invaluable provides and B Linear as known script the in recorded was language Greek the of form attested earliest The

Say they, hypothetically, the police just looked at every drivers license photo of people living in a 1 mile radius. And they find the suspect, and go to a judge saying a combination of appearance, perpetrator in suspects driveway, and criminal history gives probable cause for a search. I don’t think that’s any different.

If they came to the judge and said “an informant said we’ll find the gun here” and the informant was actually Clearview, thats obviously a problem.

The big risk that we need regulation for is not that insurance charges too much, but too little. There will always be the temptation to charge less than the other guy, get lots of customers and hope nothing really bad happens.

Using language-native packaging doesn't imply that you have to use binaries from wherever. In the pytorch example you can still build it as a regular part of the distribution, using the C++ dependencies/toolchain, it just means you don't try to stuff it into a versioning/distribution/install model that doesn't match the languages expectations.

This is conflating static linking with how the distribution handles updates. If a language is always statically linking dependencies (like Go or Rust), the distribution will have to rebuild everything that depends on a patched package whether or not they are using the language's native tools or some import into the distro package system.

What I'm specifically suggesting is:

  * Distributions package *binaries*, but not the individual libraries that those binaries depend on.
  * Distributions mirror all dependencies, so that you can (in principle) have a completely offline copy of everything that goes into the distribution.  Installing a binary uses the language-specific install tools to pull dependencies, targeting the distribution's mirror.  
  * Enough dependency tracking to know what needs to be rebuilt if there's a security update.
  * Any outside dependencies (e.g openssl) will continue to depend on whatever the distribution packages.
  * Dependencies are not globally installed, but use whatever isolation facilities the language has (so e.g, a venv for python, whatever npm does)

It’s not like this is unique to rust; you see similar issues with node and python. Distributions have many jobs, but one was solving the lack of package management in C. Now that every modern language a package manager, trying to apply the C package management philosophy is untenable. Specifically, the idea of a single version, globally installed, and producing distro packages for every language specific packages.