A few years ago, I was itching to either brush up on Java (which I hadn't used since around v1.8) or learn a new one. (eg Golang, Rust, etc) In light of Oracle owning Java, I suspected it would face a long, slow decline and would eventually fade into Perl-like obscurity and decided to spend my time elsewhere. Also, I didn't want their nagging runtime updater on my system anymore.
Haven't regretted that decision at all and it seems to be playing out about how I expected. (Except LLMs make rewrites into other languages more tractable so the slow decline of Java may accelerate)
Agreed, how could we not have datacenter capacity for the GPUs when Meta has shown that you can go from a bare field to an operational datacenter in about 3 months by using tents instead of buildings?
How hard would it be to weatherproof a GPU computing rack? Like how much more cost would it add? So theoretically you could even forgo tents. Just have them at field. Technically you could even maybe run them in freeports. Thus saving any tariff costs...
You don't even have to weatherproof the rack, putting racks into shipping containers is already done to some extent (and multiple deployments are to my knowledge working fine). It is often also marketed as "module data centers".
The main problem here is that it reduces efficiency (cooling a large datacenter is more efficient per Watt of dissipated heat than a shipping container) and increases initial cost (building in a shipping container is not actually as easy as doing it in a normal-ish building).
Portability (when offline, you can put a shipping container like this on a truck and cart it around) and availability (no need for a new/refit building, only power is required and could be included in the container with a generator (gas/diesel)) are the main reasons for accepting a higher TCO here.
It's been quite a while since I first heard about it, but IIRC they were seeding cryptographic PRNGs with entropy from multiple sources, one of which was allegedly this art installation.
Seeding PRNGs with sufficiently unpredictable data was a real security concern for a while. New cloud instances have a small entropy pool space for attackers to enumerate due to lack of a real source of randomness. (See the Debian/OpenSSL issue for what can happen when your entropy pool is too small/predictable)
One fun fact about XOR is that anything XOR'd with a uniform random distribution results in a uniform random distribution, so there isn't any harm in mixing additional non-attacker-controlled entropy sources in as long as at least one of them is sufficiently unpredictable. The lava lamps provide a potentially hard-to-predict source of entropy for this, but if it's not available then it certainly doesn't "take down the internet". They'll still use packet arrival timing, interrupt timing, etc to seed their CSPRNGs.
Yeah it really makes you think about what life would be like if intelligence could infuse anything- be it a ship or a datapad- even if his vision wasn't quite how I imagine it would turn out.
I've also seen it suggested that Harry Potter might be a more realistic look at what proliferated AI might be like.
That's not countering the argument that steering is what is preventing the bike from falling over rather than the gyroscopic effect of the wheels. You'd have to tie off the handlebars with a static line before rolling it in order to prove that it was the gyroscopic effect keeping the bike upright.
IIRC if your brokerage reports everything to the IRS properly, you only need to fill out net short- and long-term capital gains on your schedule D rather than specifying every single transaction on a bunch of Form 8949 copies.
Not sure if Double's underlying brokerage is reporting everything necessary for this to be the case though, as I believe some brokerages don't.
If your threat model includes someone with a quantum computer intercepting all of your traffic and storing it to decrypt later, you probably don't want to share your keys over a non-PQC channel unless you can guarantee that they haven't started eavesdropping on your traffic yet.
While sntrup761x25519-sha512 is a QC secure key exchange, sending a key over it doesn't count. It's not really a "pre-shared" key unless the sharing is done using organic, locally sourced sneakers. Unless FIPs, and then it's boots.
They might have been thinking of the recently discovered hardware backdoor issue, CVE-2023-38606 (see also Operation Triangulation). There was surprisingly little reporting on it.
Haven't regretted that decision at all and it seems to be playing out about how I expected. (Except LLMs make rewrites into other languages more tractable so the slow decline of Java may accelerate)