Just FYI, Amazon and most other providers offer instances that go up to many TB of ram — the largest listed on EC2 right now is 24TB.

Depending on your workload, you may get far better throughput not worrying about distributing the work and data

If you can, working with the logarithms of the intermediate large or small values is one way around the issue

One example talking about this here: http://aosabook.org/en/500L/a-rejection-sampler.html#the-mul...

Context for point 5:

- MIT sued Gehry's firm: https://thetech.com/2007/11/09/lawsuit-v127-n53

- Eventual settlement: https://thetech.com/2010/03/19/statasuit-v130-n14

> He added that “value engineering,” trimming design elements to cut costs, was the primary cause of the problems

It sounds like Gehry really made a mess of the place but also, MIT can be very weirdly cheap about some things so this also sounds unsurprising.

Carrier freezout actually makes this non-workable -- there's a limit to how cold you can make CMOS devices before they stop functioning. To say nothing of the specific heat of liquid helium, which is miniscule compared to LN2

Using a blowtorch as a heat-source is common in extreme overclocking, to heat up VRMs and memory modules up enough to boot the machine, and keep it working.

liquid helium might get into the device itself and cause other problems. (e.g. iphones stop working in the presence of helium)

That is not the free file page, and the fact that it tricks you into thinking it is is exactly the point: https://www.propublica.org/article/turbotax-just-tricked-you...

Looks like matplotlib to me (assuming you mean the top window, not the terminal or what looks like a browser behind)

Yeah, the BladeRF uses an AD9361[1] as the transceiver, which features a pair of ADCs per channel, of which there are two (so, a total of 4 ADCs and 4 DACs in the package). It's got a bunch of other convenient features like built-in PLLs both LO and baseband.

[1]

oops: [1] https://www.analog.com/en/products/ad9361.html

C-o for me, for exactly the same reason

I have a nested setup with a "meta" screen session with escape key ^Z, which holds named "project" screen sessions with escape key ^O.

I background tasks in the shell seldom enough (because I'm always in screen) that I don't regret ^Z being slightly less convenient. ^O is a fairly unknown but very useful insert-mode binding in vim, but I use emacs these days so I don't notice it being escaped.

Before I used separate escape keys, it was maddening trying to remember how many times to hit ^A to send commands to which nested session.

C-o is moderately useful in emacs to move your current line down while the cursor stays on the newly created line.

The latter can be accomplished with inverted flame graphs (sometimes called icicle graphs) which show the call stack inverted

Most of the rocket scientists I know also exercise