In an otherwise pleasant, humanist framing, they jarringly conclude Microsoft's primary AI application will be putting people into parasocial AI relationships for profit.
My choice ranking is Deno Deploy > Fly.io > AWS for new projects, depending on complexity and needs. They also have a new Deno sandbox feature which is great for running untrusted code, AI agents, etc.
The real question is can they adapt to customer feedback fast enough, focus priorities, adequately market & grow, make it profitable, etc. Bumpy road but definitely not doomed.
In a nutshell, ideally `peer.connect(remoteId)`. An API like peer-js/simple-peer. And symmetric negotiation would be great as well.
WebRTC should be the universal networking primitive for the next phase of the web, but the API exposes too many implementation details – its abstractions leak.
This plus the overall weight of integrations limit mass adoption by developers.
While WebTransport is promising, it's limited to client-server communication unlike WebRTC.
WebRTC supports peer-to-peer UDP connections as well. Thus it's better for use cases like low-latency games, video calling, and secure direct communication between devices.
A better push might be to make WebRTC more simple and modern, but I'm not sure if any standards committees are working on this yet.
You could also use JSON Merge Patch (RFC 7396) for a similar use case.
(The downside of JSON Merge Patch is it doesn't support concatenating string values, so you must send a value like `{"msg": "Hello World"}` as one message, you can't join `{"msg": "Hello"}` with `{"msg": " World")`.)
Should order this list by number of affected rather than alphabetical IMO. The 275K monthly user platform is almost hidden relative to the 49 and 300 user examples.
Excellent idea! I'd focus on the open-sourcing and community elements (e.g. creating feeds) so it can get traction, rather than features like Markdown and longer posts at this stage.
Hi real quantum physicist, yup, you pretty much got it. This is a prototype demo of the concept – and is using real IBM quantum computers. The queues are between 10s and 10min generally.
This is explained very closely to what you've said in the "Technical details" help section. Occasionally you'll get a real-time result. I'll check out the links you sent next, thank you!
Do you think qBraid could support this with more real-time latency?