↙ time adjusted for second-chance
OpenAI should build Slack (latent.space)
The meme about AMA artificially limiting the supply of new residency slots turned out to be much more complex the more I read about it (and IMO mostly incorrect, at least as described by the just-so stories on the internet where I first learned about it). The actual limiting factor is federally funded residency positions which are funded by CMMS, and were artificially capped by the Balanced Budget Act of 1997 during a widespread climate of financial austerity after Gingrich had led Republicans to retake the House in 1994 for the first time in decades. At the time, AMA apparently did release a report that included support for reducing the number of residency slots, so that detail is correct. But the decision wasn't made by them, and federal healthcare spending was already on the chopping block (and was a politically attractive area to make cuts given the Clinton's administration failed healthcare reform proposal). Starting in 2019 the AMA started regularly releasing policy statements requesting that and other caps on federal funding to be increased, but it wasn't until the CARES ACT in 2020 that Congress funded 1000 new CMMS funded slots were funded (but limited to small gradual increases each year) and started to be implemented in 2021-2022. So while there's a kernel of inarguable truth that the AMA and other medical professional groups did support certain caps back in 1997, it has always been, then and now, a policy decision by Congress. With the motivation to set limits driven by concern over federal healthcare spending inflating budget expenditures. But it makes for a simpler, emotionally resonant narrative of a shadowy self-interested group pulling the strings at the expense of the public (that also conveniently redirects outrage away from the people actually empowered to fix the problem, or that federal spending is a crucial lever to fix the problem). [1] https://www.ama-assn.org/press-center/ama-press-releases/ama-fund-graduate-medical-education-address-physician-shortages [2] https://washingtonian.com/2020/04/13/were-short-on-healthcare-workers-why-doesnt-the-u-s-just-make-more-doctors/ [3] https://www.openhealthpolicy.com/p/medical-residency-slots-congress
Where do you live? In the US, there a lot of widely available brands of UL-listed (or equivalent) wire with clearly marked specs and the cross section in ridiculous units of AWG. If it says it’s copper and it’s not an outrageous counterfeit, it’s copper. (And it will have a resistance that is in spec, because this is important for code-compliant electrical installations, and it won’t corrode when terminated properly.) And the UL-listed stuff is fantastic, because UL cares about the insulation and jacket. There is plenty of “speaker” wire with crappy insulation that degrades after a few years, but I’ve never seen an actual CL2 or CM or CL3 (or their R or P variants) or THWN(2), TC(-ER) etc, cable, from the last 30 years, with any such issues. 16AWG CL2 cable is fantastic speaker wire, and it’s cheap and you can buy it at any store that sells electrical supplies. TC-ER is great if you need something bigger than 16AWG (the longer the run, the thicker the cable you need to keep resistance below 1 ohm or so), but it’s a bit harder to find. The thing that can be genuinely hard to find is nice twisted-pair or shielded twisted-pair cable in any format other than category (Ethernet) cable, and that tends to max out at 22-23AWG and may have the wrong number of conductors for whatever you’re doing with it. For making up an RCA cable, this is completely unnecessary — use RG59 or RG6 cable if you need particularly good shielding. But for long runs of balanced audio cable, you want actual twisted pairs, 23 AWG is plenty, but you may need those pairs shielded from each other to minimize crosstalk. So you end up with commercial snake cables, and those are not cheap. Some people use digital stage boxes these days, because an effectively transparent ADC and all the electronics needed to make it work can be cheaper than the fancy cables.
> To prevent impairment of sound quality, we recommend cables with cross-sections of at least 2.5 mm² for lengths up to 3 m and at least 4 mm² for lengths above 3 m. This is just a unit issue. See: https://www.engineeringtoolbox.com/wire-gauges-d_419.html Those numbers are also ridiculous. They’re recommending 13AWG or higher for a 3m run. That’s about 20 feet round trip, which is about 0.04 ohms. The speaker should be 8 ohms nominal, but let’s call it 1 ohm at some very audible frequency to be conservative. So you might lose 2% of your power or maybe 0.1dB. Keep in mind that you cannot hear frequency-independent attention at all (the volume knob fixes it), so you’ll only hear the frequency-dependent part, which will be smaller, and your speaker plus room already has frequency dependence far in excess of 0.1dB. Note that the speaker power doesn’t even factor in to the calculation — as you supply more power, you’re increasing the current and voltage accordingly, and the effects cancel out. At very high power you may care about heating. That recommended cable has an NEC ampacity of 15A or more, and 15A^2 * 8ohms = 1800W. Derate a bit because you’re at higher frequencies than 60Hz and you are just fine — in fact, the voltage will become a safety problem at silly power long before the resistive heating matters. I will admit that there is a good reason to use at least 18AWG cable or so: speaker cable terminations are utter crap, and the crappiness seems to get worse as the fanciness goes up. A thicker wire is more likely to survive being terminated, within limits. Buy some 16AWG two-conductor CL2 or CL2R or CL2P cable at your home improvement store and be done with it. > Unless you're running speaker cables parallel to some power cables, shielding is not a requirement from my experience. I have never heard mains hum coupled from a passive speaker cable. That’s not really a thing — there just isn’t enough power to make it audible under normal conditions.
The low 8 bits of SI, DI, BP and SP weren't accessible before, but now they are in 64-bit mode. The earliest ancestor of x86 was the CPU of the Datapoint 2200 terminal, implemented originally as a board of TTL logic chips and then by Intel in a single chip (the 8008). On that architecture, there was only a single addressing mode for memory: it used two 8-bit registers "H" and "L" to provide the high and low byte of the address to be accessed. Next came the 8080, which provided some more convenient memory access instructions, but the HL register pair was still important for all the old instructions that took up most of the opcode space. And the 8086 was designed to be somewhat compatible with the 8080, allowing automatic translation of 8080 assembly code. 16-bit x86 didn't yet allow all GPRs to be used for addressing, only BX or BP as "base", and SI/DI as "index" (no scaling either). BP, SI and DI were 16-bit registers with no equivalent on the 8080, but BX took the place of the HL register pair, that's why it can be accessed as high and low byte. Also the low 8 bits of the x86 flag register (Sign,Zero,always 0,AuxCarry,always 0,Parity,always 1,Carry) are exactly identical to those of the 8080 - that's why those reserved bits are there, and why the LAHF and SAHF instructions exist. The 8080 "PUSH PSW" (Z80 "PUSH AF") instruction pushed the A register and flags to the stack, so LAHF + PUSH AX emulates that (although the byte order is swapped, with flags in the high byte whereas it's the low byte on the 8080).
 Top