algesten

Good thing Linear has been finished for a long time doesn't need more features, so AI coding can go slow. Oh damn, it's busy becoming the next Jira :(

He's optimizing for embedded no-std situation. These things do matter in constrained environments.

Are you really living your life walking around thinking about the next assailant?!

Must be terrifying.

or being... punkted?

WebSockets over TCP is probably always going to cause problems for streaming media.

WebRTC over UDP is one choice for lossy situations. Media over Quic might be another (is the future here?), and it might be more enterprise firewall friendly since HTTP3 is over Quic.

I wouldn't define it as Sans-IO if you take an IO argument and block/wait on reading/writing, whether that be via threads or an event loop.

Sans-IO the IO is _outside_ completely. No read/write at all.

> ...allows it to carry current with zero resistance at 3.5 Kelvin (about -453 degrees Fahrenheit)

Seems to me this is a problem.

Ok, pipelining as in using the fact that the socket is bidirectional, so you queue up the next request before the previous response has arrived?

Sounds a bit dodgy, since any response could potentially contain a Connection: Close. Maybe ok for some scenarios with idempotent methods.

I assume with HTTP/1.1 this would be less useful, since each synchronized request would require another socket, thus hitting potential firewalls limiting SYN/SYN-ACK rate and/or concurrent connections from the same IP.

In some respects this is abusing the exact reason we got HTTP/3 to replace HTTP/2 – it's a deliberate Head-of-Line (HoL) blocking.

One thing I toyed with, but didn't get very far, was to encode the HTTP/1.1 protocol as a Sans-IO state machine with .await points for the IO, but rather than the IO registering Wakers with an async runtime, it relinquished control back to the user to perform the IO manually. One can think of it as .await releasing "up" instead of "down".

In the context of HTTP/1.1 the async code became a kind of "blueprint" for how the user wants the call to behave. At the time I was dead set on making it work for no_std (non allocator) environment, and I gave up because I couldn't find a way around how to need dynamic dispatch via Box<dyn X> (needing an allocator).

In fact, not being able to do some of these things might improve privacy.

Yeah. It's going to be great. Selected experts are saying so.

I think the important thing is that the semantic index tracks all you do through all your apps.

"Semantic Index" sure is a better name than "Recall". Question is whether I can exfiltrate all my personal data in seconds?

The article says "the government has called the bill “fundamentally flawed”, but there may be sufficient House support to turn it into binding legislation"

Sounds like Trudeau is not the problem in this instance?