Object capabilities, like capnweb/capnproto?
The vulnerable code exists inside of the React Flight wire protocol that is used by Next.js but also Vite, Parcel, Waku and any other custom RSC implementation that exists. Your comment was accurate circa 2019 but not…
The React Server Components wire format (Flight) is relatively novel and very new (it has existed in React stable for just a year). This is not a simple JSON parsing bug.
Record types are now "on protocol", you resolve them via a similar mechanism as in the article. https://atproto.com/specs/lexicon#lexicon-publication-and-re...
And Vercel's "compute units"
ZigBee is a mesh network, this is very important in many situations eg. battery powered or large area
1.0.0 means the API and semantics are stable, not that there are no bugs.
Observables and Generators (iterators) are fundamentally different. Observables are push-based (like a promise) whereas iterators are pull-based (like a function). Glossing over this fact leads to a flawed…
Things mostly just work. Remember Node.js is mostly APIs on top of JS the language. If those tools compile to JS in the browser, they can compile to Deno. Deno is a more stabdards-based runtime than Node, it's closer to…
I wouldn't agree that Deno showed that, as I said many companies are making a lot of money from non-Node JS runtimes. The players I mention have built their own runtime, they're mostly all built on V8 isolates…
Deno isn't the only company offering a not-Node JS server runtime. Cloudflare, Shopify, Fastify, AWS, and probably more all have skin in this game.
Unsafe does not turn off the borrow checker https://steveklabnik.com/writing/you-can-t-turn-off-the-borr...
One of my favourite things about Remix, and where it beats Next IMO, is that you can deploy it anywhere. Bring your own server. Whereas trying to deploy Next.js anywhere other than Vercel is a nightmare.
You're asking for opaque types. This is kinda possible in typescript but you can only approximate it unfortunately. You may also want to consider a branded type, which can be useful but a little less strict.
I think this article skips over many nuances of the declarative model. For a real "ground up" approach of explaining those I'd recommend this article series: https://acko.net/blog/climbing-mt-effect/
It's a common phrase in East Anglia in my experience.
Object capabilities, like capnweb/capnproto?
The vulnerable code exists inside of the React Flight wire protocol that is used by Next.js but also Vite, Parcel, Waku and any other custom RSC implementation that exists. Your comment was accurate circa 2019 but not…
The React Server Components wire format (Flight) is relatively novel and very new (it has existed in React stable for just a year). This is not a simple JSON parsing bug.
Record types are now "on protocol", you resolve them via a similar mechanism as in the article. https://atproto.com/specs/lexicon#lexicon-publication-and-re...
And Vercel's "compute units"
ZigBee is a mesh network, this is very important in many situations eg. battery powered or large area
1.0.0 means the API and semantics are stable, not that there are no bugs.
Observables and Generators (iterators) are fundamentally different. Observables are push-based (like a promise) whereas iterators are pull-based (like a function). Glossing over this fact leads to a flawed…
Things mostly just work. Remember Node.js is mostly APIs on top of JS the language. If those tools compile to JS in the browser, they can compile to Deno. Deno is a more stabdards-based runtime than Node, it's closer to…
I wouldn't agree that Deno showed that, as I said many companies are making a lot of money from non-Node JS runtimes. The players I mention have built their own runtime, they're mostly all built on V8 isolates…
Deno isn't the only company offering a not-Node JS server runtime. Cloudflare, Shopify, Fastify, AWS, and probably more all have skin in this game.
Unsafe does not turn off the borrow checker https://steveklabnik.com/writing/you-can-t-turn-off-the-borr...
One of my favourite things about Remix, and where it beats Next IMO, is that you can deploy it anywhere. Bring your own server. Whereas trying to deploy Next.js anywhere other than Vercel is a nightmare.
You're asking for opaque types. This is kinda possible in typescript but you can only approximate it unfortunately. You may also want to consider a branded type, which can be useful but a little less strict.
I think this article skips over many nuances of the declarative model. For a real "ground up" approach of explaining those I'd recommend this article series: https://acko.net/blog/climbing-mt-effect/
It's a common phrase in East Anglia in my experience.