> But there's one performance-related area where the Framework pulls ahead—a little—and that's sustained performance. When running a heavy workload like HPL (a FP64 HPC task, that taxes the CPU and RAM constantly for many minutes), the Framework's fans allow it to throttle less than the Neo.

People are seeing big gains in sustained performance on MacBook Neo with a simple thermal pad mod. The disadvantage is the underside of the Neo can get hot, but that's not an issue if it's sitting on a desk instead of your lap.

I was all in on Svelte and SvelteKit until I started encountering CSS weirdness caused by a bug that the Svelte developers said is "by design", namely that components' CSS isn't removed from the document after the last instance of that component is no longer rendered. This resulted in a situation in which styles became dependent on the navigation path the user takes, leading to weird an unpredictable layout issues. I couldn't stomach solving this by using Tailwind.

Then Svelte 5 came along and made Svelte more like React. At first, there were just a few simple runes, but then the runes started proliferating like crazy to solve other runes' problems. At that point, Svelte was dead to me and I went back to React/Next.

The right path for Svelte to take would have been to continue to refine Svelte 4.

Interesting, so if I'm understanding correctly, component A's style was supposed to change when component B was present, and this was implemented as styling rules in component B? Why was Tailwind necessary rather than moving these rules to component A (which I know would probably require some gnarly selectors)?

I don't want to be a "you should've double bagged it" guy, I'm just curious. Svelte is not the be all and all, if you moved on to greener pastures more power to you.

I love how I can see the HTML being streamed onto the page in real time, like the good old days of dialup when images gradually rendered from top-to-bottom.

Brings memories. How my school trashy dial-up was so unbearably slow compared to my father's work 128 ISDN. On latter, I was able to even download several songs per visit from ftp, and later from Napster.

It's for Google.

Perhaps, but I think that by the time we're that far advanced, strokes will be entirely preventable.

Strokes will never be preventable. You can mitigate them but a stroke isn't really a disease. It's a symptom.

An ischemic stroke (i.e. stroke due to a clot) caused by vascular or cardiac issues can be mitigated. A cryptogenic stroke however is idiopathic and therefore has no understood cause. These types of strokes make up 30-40% of all strokes. Unless we figure out their cause, there's no way to really prevent them.

But then there's also hemorrhagic strokes which are an entirely separate category that has causes and mitigations more or less diametrically opposed to those for ischemic strokes.

And of course those are just your broad painted categories and they are generally looked at as the start of a medical emergency but strokes happen all the time as a consequence of other medical emergencies.

Even if you could perfectly prevent strokes in generally healthy populations, those same people may still end up suffering from a stroke during a surgery or during/after a major accident or injury. No amount of preventative medication can prevent someone suffering a stroke caused by a brain bleed after a car accident. Likewise for someone with a crush injury, internal bleeding, or broken bones that end up throwing a clot which makes it into the brain.

So any advancement in halting and reversing damage from a stroke will be a massive boon for emergency medicine until the end of time. Unless of course we somehow find a way to cure/render humans immune to blunt force trauma or lacerations.

Sure you can. Just not with any technology on the horizon. But there is conceivable technology (e.g. medical nanotechnology) that could prevent strokes or stop them as they are happening.

Like what?

Like detecting constriction or loss of integrity of blood vessels, and doing the corresponding intervention.

The saddest thing here is not that it requires some future nanotechnology, but is achievable at the present scientific level, yet too expensive to develop, and wouldn't see FDA permission in a decade or two anyway.

There's nothing stopping you from setting up your free (as in freedom) slice of cyberspace for you and your friends, for now.

Looking at all the new and proposed laws coming through, I don't think we'll have those basic freedoms all that much longer.

Taking a brief look at wizball.asm, it actually used 200 Hz interrupts on both PAL and NTSC. The timings are shown from line 39.

RAM can be increased to 16 MB and CPU speed to 48 GHz.

I’m sorry how many Hz???

The 64Ultimate goes to 64MHz, the Ultimate64 cartridge goes to 48MHz "only".

It's a stealth subscription product. People are losing those things all the time.

And if not losing, the battery dies in 2-3 years, so you'll have to buy new anyway.

Eh, mine are four years old and still going strong. Battery still lasts longer than I need it to.

Like all other bluetooth in-ear phones.

The C64 does have a couple of bitmap modes. The Last Ninja uses mode 3, which is multicolor bitmap mode. It occupies 9000 bytes including pixels (8000 bytes) and color RAM (1000 bytes).