The old, bug-ridden native XSLT code could also be shipped as WASM along with the browser rather than being deprecated. The sandbox would nullify the exploits, and avoid breaking old sites.
They actually thought about it, and decided not to do it :-/
I don't know if the evidence is more than anecdotal, but I've read that ADHD smokers who are taking adderal have to increase the dose of their treatment to remain functional when they quit smoking.
I've been taking nicotine patches for half a year now, with great success (and it is available OTC unlike other stimulants). Nicotine in itself isn't toxic at these doses (7, 14, 21mg), it's a cool life hack :-).
I enjoy cigars and notice the positive effect, my fear with the patches or Lucy/zyn is that it not being self limiting seems to lead to people having one in their lip literally every waking minute when they’re not eating.
Patches are changed once per day, and their pharmacokinetics isn't addictive (the nicotine blood levels rise too slowly to give you a dopamine boost).
I sometimes realize in the afternoon that I forgot to change my patch in the morning because I'm a bit drowsy (a feeling not unlike being uncaffeinated when you're used to drinking coffee). AFAIK the withdrawal symptoms fade out in at most a week.
I've had a similar problem with WebGPU and WGSL. LLMs create buffers with the wrong flags (and other API usage errors), doesn't clean up resources, mix up GLSL and WGSL, write semi-less WGSL (in template strings) if you ask them to write semi-less [0] JS...
I have been sleeping on this for quite a while (long covid is a bitch), but I have built a benchmarking lib that sidesteps quite a few of these problems, by
- running the benchmark in thin slices, interspersed and suffled, rather than in one big batch per item (which also avoids having one scenario penalized by transient noise)
- displaying a graphs that show possible multi-modal distributions when the JIT gets in the way
- varying the lengths of the thin slices between run to work around the poor timer resolution in browsers
- assigning the results of the benchmark to a global (or a variable in the parent scope as it is in the WEB demo below) avoid dead code elimination
This isn't a panacea, but it is better than the existing solutions AFA I'm aware.
There are still issues because, sometimes, even if the task order is shuffled for each slice, the literal source order can influence how/if a bit of code is compiled, resulting in unreliable results. The "thin slice" approach can also dilute the GC runtime between scenarios if the amount of garbage isn't identical between scenarios.
I think it is, however, a step in the right direction.
In both case, if you've used JSPerf you should feel right at home in the WEB UI. The CLI UI is meant to replicate the WEB UI as close as possible (see the example file).
I hadn't run these in a while, but in the current Chrome version, you can clearly see the multi-modality of the results with the dummy Math.random() benchmark.
Amusingly, the word anatomy (“dissection”) is from Greek via Latin, from the very same root that we’re discussing here.
Other English terms from the Greek root for “cut”: tomography (imaging through a lot of cross-sections); entomology (study of in-sects, critters with sect-ions in their bodies); dichotomy (division into two possibilities); atom (that which cannot be divided).
“Up” or “thoroughly”, apparently? Same prefix as in analysis, anaphora, anamorphism. Ancient Greek had a sprawling system of prefixes that one can’t really pick up by osmosis, it seems.
(Complaints about noun morphology sound a bit hypocritical from a native speaker of Russian, I know, but it is what it is.)
They actually thought about it, and decided not to do it :-/
reply