Thanks for typing that out. Note that your answer can't be right, though.

Thank you for this comment. I learned a lot.

https://web.archive.org/web/20...

I.e. "It does."

You're off by a factor of 10x.

Starlink is at 480-550 km
Amazon Leo is at 590-630km

At most that's about 30% the distance or about 30% more latency. Also an extra round trip of 300km is about 1ms extra latency.

Just because they don't make it doesn't mean they can't license the patent to the foundries.

Probably not but there are two existing datacenters downtown along with Seattle Internet Exchange. Not a lot of room to expand though I imagine in the building.

cootys rat semen

Denotating it is exactly what the Bluetooth name does. *Detonating* it, on the other hand...

You realize that's the point, right?

For int'l flights: Amazon Leo is launching next year. Delta is waiting.

And LEO is even easier than GEO since it doesn't have any moving parts. GEO had to rotate to keep alignment. LEO are all using phased arrays.

For existing code in the QA he said leave it be and it's better to fix.

For new code, he's recommending Rust and the advantage he talks about is that it makes the code more maintainable by people. And one thing that every AI coding talk I've seen agrees on is that what makes code more maintainable by people also helps AI and vice versa.

People and AI both have limited attention and memory. The less context necessary the easier it is to evaluate safety.

Another thing not in the summary he touches on is hardware safety. Not just software bugs but also compromised hardware which if your driver is memory safe can also prevent a buggy or adversarial piece of hardware since the hardware is effectively user input.

To balance out OP's selective quoting to avoid people strawman-ing his argument as a fanatic who can't balance risk:

I seem to have had a very similar progression. I still tend to think in "/." replacement operators, but it's been perhaps 15 years since I've really used Wolfram Language.

Do you really say "lol"?