Keep on reading the papers.

The key thing to make QC work is the ability to do logic on error corrected qbits with scalable error correction.

We are not remotely close and there's no sign of a plan to get there.

The quantum surface codes and quantum LDPC stuff that claimed to solve the problem clearly do not. You just have to read the papers and find the bit where it gives the error correction capability vs the unreliability of the underlying non error corrected qbits. Compute the binomial error distribution for factoring a 1024 and 2048 bit RSA. You will find just how fantastically far away we are from having a working quantum computer.

All the technical people I know use Signal.
Those of us conversant in cryptography have studied the protocol and found it to be good.
The ratchet, oblivious RAMs, good algorithm choices and much more.

It reads more like they did the logical thing.

ML-KEM is the new NIST standard for transferring a key (ML=Modular Lattice, KEM=Key Encapsulation Method). It's the default choice for a post quantum KEM.
With the ratchet, the logical thing to do is to tack on a third cog using ML-KEM. That's what they did.
Also you need to accommodate the huge numbers that ML-KEM uses. That's what they did.

It's a fine design, done well and deserving of praise - especially deploying a hybrid scheme against the best efforts of the NSA to stop that, but I don't think it counts as an amazing engineering achievement.

Calling is SPQR is pretty funny for someone who grew up in a formally Roman fortress town.

I've been through the Lenovo series of connectors. I worked at Intel for 21 years and they were a Thinkpad/Lenovo house. I got my mother a Lenovo on the grounds they're a bit less prone to fall apart than other brands. Macs weren't in the running because she uses windows specific software. I have my yellow tipped barrel connector adaptor secreted in box for when the occasion to use it arises.

The (quite new) MacBook Air I'm typing on has 2 USB-C and one Magsafe 3. The real issue is I have only a single Magsafe 3 cable while I've got lots of USB-C chargers and cables so when the other ports are occupied, I'm schlepping off to find the one single cable. I tend to run lots of CPU heavy jobs, so it's the higher power brick for me.

But that ARM CPU. Ugh. I've hated the ARM instruction set since the Archimedes. It's not got better. They messed up the RNG instructions ( https://developer.arm.com/docu... ) stipulating 90C-RBG3(RS) structure which is the wrong choice for an instruction-as-full-entropy-source (Like RdSeed on Intel). The 90C-RBG3(XOR) is the right one since the RBG3 doesn't block the RBG2 with the XOR construction. RISC-V made the same mistake in their drafts, but they listened to my arguments and fixed it. ARM wouldn't give me the time of day and so here we are with broken specs for ARM. I wouldn't care if engineering RNG things wasn't what I did most of the time.

There's always the Framework running Linux when I want to retreat to my happy place. 6 ports, all configurable, X86 CPU and das blinken lights on the keyboard.

Great, I'll use my old MacBook charger.
Oh no! it's a MagSafe 1.

I guess I'll get the slightly newer MacBook charger.
Oh no! It's a MagSafe 2.

I guess I'll use the MagSafe 3 that came with the new laptop.
Oh no! It's not there.

It's a good thing I never enabled secure boot on my Framework laptop.

In the US, the push for non hybrid is all coming from the NSA.
The NIST people know this but can't say it publicly.
There was a pretty much unanimous consensus for hybrid schemes at the most recent ICMC.
I've been saying this since it became a thing which was pretty much at the last ICMC where NIST announced the deprecation of hybrid schemes.

What are the odds that they have a classical break of ML-KEM, or ML-DSA? SIKE was a finalist a fell to a classical attack.

The is the Dual-EC-DRBG all over again. It's good that DJB is raising it. People listen to him.

I don't use wireless buttons. I just use my phone. But I've been putting things in the house under control of HA bit by bit. The mini splits, the lights, the TV, lamps, door locks, EV charging and more are all controlled by HA. With a port forward and dynamic DNS, I can control this stuff wherever I am.

It's a 100 year old house. So updating the wires has to precede any z-wave plugs or lightswitches in any given room. I'm about 70% done so far.

That is where Home Assistant shines. You can create all manner of automations and it will work with most devices. So if there's a z-wave or zigbee lightswitch, you can use home assistant to get your input of choice to control it.

I don't know the specifics of your situation, but I'm pretty sure that if you have something that works for you, you don't want Logitech to brick it one day.

I connect it to the wifi so I get the updates overnight. If I'm not at home I can tether to my phone via wifi and get updates that way. Unlimited data on the phone is handy for that.

>OTA updates cost automakers $66.50 per vehicle for each gigabyte of data, Harman Automotive estimates.

What nonsense. When Tesla sends an update. it comes in over the internet, to my house and onto the car via wifi. I'm guessing Tesla isn't paying $66 per gigabyte for their ISP service and neither am I.

What's ludicrous? Having a career? Working for money? Following the prescribed visa processes for working in the US?

Since leaving my mega corp of the past 21 years, I've been working with startups. They uniformly don't give a shit where employees are. Everything is online and people are employed all over the world, where they are.

When you care about the costs, efficiencies and efficacies of engineering, WFH is the best option for design work. The data supports it and small companies are way more sensitive to costs. RTO is the preserve of large companies with lots of case and warped priorities.

>I've always wondered if it's true or not that the mostly Indian workforce in US is paid way below.

I came in on an L1 for a temp assignment. I was paid competitively. I did bring specific skills that were unavailable otherwise.
25 years later I'm still here. VP of engineering in a tech company and doing ok.

I'm not Indian though, although I work with many. Skills tend to count over origin in my field.

The author doesn't know the differences between WiFi, fiber and the internet.