afiori

To be pedantic the ad hominem fallacy is about trying to deny an argument by attacking the author, so in a discussion about zig Vs rust if Andrew isn't trying to enter the discussion and just argue "that guy was stinky, glad he is gone" is not really an ad hominem, just not classy let's say.

Just use unsafe then

I agree with your point, but for completeness:

> How is not having to mark your unsafe code as unsafe a good thing?

The problem with unsafe code in Rust is that IIRC nobody actually figured out yet the "rules" of unsafe i.e. which invariants you can stretch and which can cause UB. My (not super up to date) understanding is that this is an active area of research and progress is being made and also that in practice there are many well understood usages.

In short unsafe rust is somewhat worse than C++ as the boundaries of UB are less well understood/defined

A tool to do automatic migrations eg react often publ

This looks like something only a libertarian would like

Well people that have been hearing of the slippery slope fallacy their whole life might end up biased against such an approach

Regexes should have been a structured language not an hodgepodge of DSLs

The issue is that many modern DOM APIs assume js semantics and types (eg promises, iterables, etc) so you need to "reimplement" some js semanthic in wasm; sorta like how apple added a few custom instructions on the M1 chip specifically for the type of floating point operation required by js.

Which makes me think that I have never heard of signed images/artefacts

I understand ai hate but I would rather avoid a future where everybody talks in purposely weird and unstructured sentences to avoid being similar to ai

By necessity a lot of people write very similarly to how llm do

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.