afiori

This does not address how much the JWT header is a security footgun (eg you can inline remote keys into the header). if you are doing something simple you can disable all "advanced" features and be pretty safe but if you are doing something a bit more complex it is not so easy.

The only case where JWTs are actually useful is when the producer and consumer do not share a DB (eg OAuth/OIDC, iot deployments, heavy microservice architectures) otherwise a good cached session store should handle well up to a few orders or magnitude below google scale.

Conceptually maybe you can compile flash to SVG+js but this has nothing to do with the point. Many insist (I have no direct experience) that the flash ecosystem (especially the editor) was and is unsurpassed as a publishing platform for interactive experiences.

Today with the current focus on mobile+low latency+e-commerce optimizations flash would probably have shown a lot of limitations, yet JavaScript, SVG, canvas, http webgl etc still fail to provide a "competitor" to what flash used to be.

The web simply went in a different direction, one that left many unsatisfied

oh no, a new edge case tech has not replace the most popular tech stack ever, yet another failure after webGL

Sure, figma is 6% of the internet

Asking for 0% js 100% wasm website is like wanting a C-free linux distro

Java's vm does not start in milliseconds nor has dozen independent implementations in every ecosystem

Because Java was doing nothing similar, a better comparison would be .NET CLR that actually tried to be a decent compilation target.

Also security, Java has reflection so you cannot reliably sandbox java libraries

This comment starts with a no, but agrees with the parent...

Long term archival is often also about long term support and there just going with the most popular/supported ones might be a safer bet, eg in the extreme case if I wanted to save some digital photos in a time capsule I would likely choose PNG and JPEG

Maybe even split it into a set of small reusable coherent utility classes

federations are the only decentralization model that scales, the issue is that most "federated" systems are actually just "distributed centralization" eg mastodon.

In cryptosystems there is a difference between things that can be changed and not, eg passwords/keys are a secret that can be easily charged. Algorithms not so much.

"Security through obscurity" refers to the practice of using an hard to change "thing" as a secret, which is indeed bad practice

The US and its allies are likely the biggest sponsor of terrorism and genocide worldwide

Naval blockades are an act of war even according to US own laws.

The hosts file is enough, what is needed is a way to assign an ip address to a process/service like you can with port numbers.

Imo there would be ways to do it so that it could have a similar effect to the capitalized nouns in German

Some come to async from callbacks and others from (green)threads.

If you come from callbacks it is (almost) purely an upgrade, from threads is it more mixed.

Pardon power competes with governors (at least NY) being able to edit laws before signing them for most anachronistic/dystopian feature of the US state.

yes, with a but, rephrased as "crazy that you can't use a private service without payment or otherwise contributing to its profitability" sounds less so crazy.

I agree on the excess.

Don't forget about pardon power.

Considering how hard US military bases and radar systems have been hit (and those are not city-sized target) I am unconvinced that even AMZN's pocket change could realiably protect against the kind of attacks we see in this war

being able to customize the chunking/diffing process with something analogous to an lsp would greatly improve this. In my experience a particularly horribly handled case is when eg two branches add two distinct methods/functions in the same file location (especially if there is some boilerplate so that the two blocks share more than a few lines).

a language aware merge could instead produce

>>>> function foo(){ ... } ===== function bar(){ ... } <<<<<<

iirc ours is always the commit the merge is starting from. the issue is that with a merge your current commit is the merging commit while with a rebase it is reversed.

I suspect that this could be because the rebase command is implemented as a serie of merges/cherry-picks from the target branch.

With Cathode ray TVs only a single pixel at a time is on, it relies on our eyes having bad enough temporal resolution, if you have Superspeed eyes you will see just a coloured line/pixel moving on screen

Just like many languages have annotations for inlining functions they could have annotations for tco. From an usability pov i would like annotations for must, must not, should, and should not. Where the "must" versions error if the compiler can't do the optimization

based on recentish interviews (or book?) it was likely genuine in the sense of not being performative, but apparently she knew it was both false and the wrong thing to say but said it anyway out of loyalty to Biden.

Intra-party elections should definitely be some variant of ranked-choice voting. To at least try to avoid the current fractal polarization.

The web part is the security model and the tradeoffs between security and performance. PNaCL was in browsers but not "web" for this reason.

Like the assembly part means low-level and meant as a compilation target, not CPU instructions.

So websssembly is an assembly language for the web, like webgl is opengl for the web and webgpu are gpu APIs for the web. And behold none of those can access DOM APIs

{"$temporal_type":"PlainYearMonth","$data":"........"}

The us is indeed very interested in how many innocents its enemies kill.

70 years of bombing random coutries an causing caos and military dictatorships show that is might not apply inward.