tarlinian

Isn't the real reason to use char8_t over char that it that char8_t* are subject to the same strict aliasing rules as all other non-char primitive types? (i.e., the compiler doesn't have to worry that a char8_t* could point to any random piece of memory like it would for char*?).

Elpida was purchased by Micron after the financial crisis (they bought it out of bankdruptcy for a swan song in 2013). Much of the Micron DRAM you might buy is made at the former Elipida fab in Hiroshima.

Thank you for the link to Robin Sloan’s blog and temporarily answering my question about whether I should upgrade iOS. I love his books and for some reason never thought to look to see if he wrote anything else online.

This just doesn't make technical sense. I completely agree that backdooring encryption standards is a bad thing. But Dual EC DRBG is a clear example of a NOBUS backdoor actually being that. The backdoor is equivalent to "knowing" a private key. The weakness is not some sort of computational reduction. Using this logic, you would say that no encryption method is possibly secure because you can't rely on its security once the key is exposed.

Plenty of actual research costs count as overhead to avoid the need to hire an army of accountants to allocate every single bit of spend.

For example, the electricity costs of the lab in which the research is run would typically be paid for by the university and would be considered overhead. It's not "administrative bloat". Most of the particularly gross administrative bloat is on the undergraduate side of things where higher tuition costs have paid for more "activities".

I think the "X" looks like a pair of scissors. No good explanation for ZUndo though.

I like how you edited this to add "at work" after folks provided examples of it happening outside of work. If you'd like a slightly more work adjacent example, see the rampant increase in IEPs for students in the bay area. (I'm sure that the increased time for tests provided in many of these cases is not being abused at all...)

How did you choose the process noise covariance in your `grad` function? It doesn't seem like a single process noise covariance structure should be globally applicable across all possible functions.

This headline kind of misses the point. The NTSB is very explicitly structured to not be a regulator to enhance cooperation between all parties, which is part of the reason that confidentiality is so important.

To be clear, you want to decrease the permittivity that adds capacitance where the accumulation of charge serves no purpose (i.e., in the interconnects) and increase permittivity where we want to have a lot of charge (i.e., on the actual transistor gates so we can produce a large enough electric field to switch the transistor), which is why gate dielectrics use high-k materials like HfO2 and interconnect layers use low-k dielectrics like carbon-doped oxides.)

A red LED (or really any LED due to the physics of the type of energy transitions used to produce light with an LED) has a much shorter wavelength (significantly higher energy photons) than any type of EM wave sued for cellular connectivity (including the mm-wave stuff that isn't being deployed very widely).