smaddox

> though we did not delve into the observation

Oh, the irony.

Gold/M2SL(Billion USD) is currently around 0.12. In 1980, it peaked around 0.45. Monthly average since 1960 is 0.11. In late 2011 it peaked around 0.18.

Gold / Global M2 would be a better metric, but I haven't analyzed that yet.

I switched to Windsurf.ai when cursor broke for me. Seems about the same but less buggy. Haven't used it in the last couple weeks, though, so YMMV.

For those who are actually interested in this field, the proper way to measure this would be with a four point probe. You do need a constant current source and a high-impedence voltage meter, though.

Also, you don't need to solder wires to the sample. But if you want to measure the hall resistance of a thin film of a semiconductor, you can solder a glob of indium on to four corners of a 1 cm x 1 cm wafer, put it in a magnetic field, and then do basically the same measurement as four point probe, except not inline.

> That application was submitted in March 2024 and is on track for approval in December 2026

Huh? Is this something where there's multiple incremental steps in the process, and that date is just the final approval stamp, or does it actually just take more than 1.5 years?

Oh, interesting. 120db is much better than what I thought possible with CMOS sensors. Thats competetive with the human eye.

Well, that definitely changes my opinion on how feasible/competitive camera-only autonomous driving can be.

> if you compare Intel's headcount with comparable companies (AMD, Nvidia), you can see Intel is really wasteful

AMD and NVIDIA are fabless. They are not comparable. It takes far more people to R&D a cutting-edge process node and run a dozen fabs 24/7 365.25 than it takes to design cutting edge chips.

If both sides are frosted, then you will have a similar effect as subsurface scattering.

I've been using this for a few weeks now, and it's really handy. But I did learn the hard way that it fails if you don't have internet connection, even if you already have the venv cached.

Not the OP, and not at all an expert in this area, but I was curious what the answer was, and from a bit of reading it seems like a potential reason that might not work is because volatile also prevents caching the value in a register. So if you want to keep the computation in a register, but you want to explicitly clear the value to zero before writing to it, it seems like C semantics are insufficient (at least without inline assembly).

The slowdown is in the simulation, not in the internally perceived flow of time. The internally perceived flow of time would of course not change.

The problem is that an exponential slowdown at each level requires discounting the probability of being in a simulation by an exponential amount per level. So instead of being able to say that the weighted odds of being in a simulation are higher than the odds of not being in a simulation, you have to say that, at best, there's a small chance of being in a simulation.