Quic (ha) thing:
Webtransport on Firefox currently has issues See: https://bugzilla.mozilla.org/show_bug.cgi?id=1969090
Readit Newsvalorzard commented on The first Media over QUIC CDN: Cloudflare moq.dev/blog/first-cdn/... · Posted by u/kixelated
valorzard commented on The first Media over QUIC CDN: Cloudflare moq.dev/blog/first-cdn/... · Posted by u/kixelated
Chrome and Firefox support WebTransport. Safari has announced intent to support it and they already use QUIC under the hood for HTTP/3.
Cloud services are pretty TCP/HTTP centric which can be annoying. Any provider that gives you UDP support can be used with QUIC, but you're in charge of certificates and load balancing.
QUIC is client->server so NATs are not a problem; 1 RTT to establish a connection. Iroh is an attempt at P2P QUIC using similar techniques to WebRTC but I don't think browser support will be a thing.
Last I checked, Iroh is gonna use WebRTC datachannels to run QUIC over SCTP
valorzard commented on TextKit 2 – The Promised Land blog.krzyzanowskim.com/20... · Posted by u/nickmain
I was really excited by the title that this would be about beloved classic Minecraft mod pack Tekkit
Would this (eventually) include the unreliable datagram extension?
valorzard commented on When Is WebAssembly Going to Get DOM Support? queue.acm.org/detail.cfm?... · Posted by u/jazzypants
Disclaimer: I work on Jco, one of the user-facing Bytecode Alliance WASM JS ecosystem projects
Just a note, but there is burgeoning support for this in "modern" WebAssembly:
https://github.com/bytecodealliance/jco/tree/main/examples/c...
If raw WebIDL binding generation support isn't interesting enough:
https://github.com/bytecodealliance/jco/blob/main/packages/j...
https://github.com/bytecodealliance/jco/blob/main/packages/j...
https://github.com/bytecodealliance/jco/blob/main/packages/j...
Support is far from perfect, but we're moving towards a much more extensible and generic way to support interacting with the DOM from WebAssembly -- and we're doing it via the Component Model and WebAssembly Interface Types (WIT) (the "modern" in "modern" WebAssembly).
What's stopping us the most from being very effective in browsers is the still-experimental browser shim for components in Jco specifically. This honestly shouldn't be blocking us at this point but... It's just that no one has gotten around to improving and refactoring the bindings.
That said, the support for DOM stuff is ready now (you could use those WIT interfaces and build DOM manipulating programs in Rust or TinyGo or C/C++, for example).
P.S. If you're confused about what a "component" is or what "modern" WebAssembly means, start here:
https://component-model.bytecodealliance.org/design/why-comp...
If you want to dive deeper:
You should write an article about this stuff and post it here since this is the first time I’m hearing about all of this
valorzard commented on A Mental Model for C++ Coroutine uvdn7.github.io/cpp-coro/... · Posted by u/uvdn7
> I’m not totally sure if this is a GOOD idea to add to the c++ standard
What are the downsides? Naively, it seems like a good idea to both provide a coroutine spec (for power users) and a default task type & default executor.
well, Rust didn't do the same thing for a reason. Rust lets you pick and choose what async runtime to use (even though everyone has decided to use Tokio anyways). This is good because it allows for alternative async runtimes like Embassy (https://embassy.dev/) and it also doesn't freeze the API into something that can't change. It could totally be possible that people find a new style of async that works better than std::execution.
valorzard commented on A Mental Model for C++ Coroutine uvdn7.github.io/cpp-coro/... · Posted by u/uvdn7
I am not a native speaker and I joke about my typos and grammar mistakes being the evidence that none of my code or post is AI generated.
Sorry about the typos. I just fixed all the ones I can find. Hope it's better now.
i appreciate that you don't use AI. I like real human stuff
- What is he using now? (Python?)
- Is there a LISP dialect that doesn't suffer from this problem? I can see that from time to time LISP projects start taking off just do die a year later and I'm stuck using Emacs (Lighttable comes into mind)