stefan_lec

YouTube rebroadcast of official SpaceX feed (h/t NasaSpaceFlight forums):

https://youtube.com/watch?v=fmkHjDeECps

Also hosted directly on SpaceX website:

https://www.spacex.com/launches/starship-flight-14

AA isn’t testing different harnesses there, they’re testing different models on the same common harness:

“We run Terminal-Bench 2.1 with the Terminus 2 agent harness in an e2b sandbox and report pass@1 averaged over 3 repeats per task.”

This is a different agent harness than those Strands was testing with, and there’s no guarantee the pass criteria matches up the same either.

Yes, but a big reason payloads cost so much is the need for extreme mass optimization, which is driven entirely by limitations in launch technology.

When launching large masses to high energies gets cheaper, payloads have a chance to get cheaper, too.

How do these perform for cold-starts? I remember one of the disadvantages of using web assembly for Workers was more spin-up time, but maybe they figured out a way around that.

Have you tried Astro? It lets you do exactly that: server-side rendering with HTML templates in component form, with css scoped to the component. No shadow dom needed, no JS frameworks either.

Very handy for nav bars with expandable drop-downs for more links - can now be done with zero JS. Requires much less CSS boilerplate now, and you don’t have to use z-index at all (which eliminates a whole bunch of tricky issues). They also handle all the tricky aria/keyboard/focus mgmt bits for you, too. It works really, really well.

Supposed to be real handy for tooltips too, but haven’t used that myself yet.

Edit to avoid potential confusion: these are separate from modal dialogs, think more like very small popups anchored to one point on the page that still allow you to interact with everything else. Theoretically you can make them modal, but it would be silly to - you’d be better off using <dialog> and the invoker api

Something about this feels very Tolkien-ish.

Nobody mention it to Peter Thiel, he doesn’t need any more ideas.

Where’s my nanometer-sized violin? Always losing that darn thing …

Sounds pretty cool! I wonder if it closes enough holes that we could finally stop using SPF at all?

I’m a bit skeptical of the accuracy of the traffic data claimed in this article, 30% of users not being able to use baseline widely available features is a suspiciously large number. Unless this is a very unique set of users, I doubt that it is accurate. Maybe bot traffic messing up the data?

For context, baseline widely available requires that your browser have updated at some point in 2023, which happens automatically for almost all users. For mobile devices, any device that supports Android >= 7.0 or iOS >= 17 would meet this requirement. Chrome even supported Windows 7 through Feb 2023, too.

According to this: https://www.digitalapplied.com/blog/mobile-os-market-share-2...

* iOS >= 17.0 covers 95% of global active iOS devices

* Android >= 7.0 covers at least 99% of global active Android devices

It seems reasonable to me to drop support for Windows XP, IE, and phones that are a decade or more old (iPhone 8, Galaxy S5). And if you claim to be supporting stuff that old, but you don’t test your site on it, you’re just kidding yourself.

You have to draw the line somewhere.

Because they couldn’t get the cats to pose obediently for the artist?

Biggest things changed are the plumbing inside the booster (much beefier, now supports starting all engines at once), and a new version of the engines, raptor v3 (more robust, and saves about 1 ton of mass per engine).

Cool image comparing the three versions of the engine. In addition to making the engine itself a bit lighter, moving all that stuff to the inside of the engine let them eliminate a whole bunch of heavy shielding in the engine bay.

https://ibb.co/pr0gx688

Yeah, the new raptors and engine bay redesign for version 3 of ship seem a lot more robust than version 2, very impressed that the ship finished its mission so well.

Scott Manley goes into quite a bit of detail on analyzing superheavy’s failed boostback, it’s a good watch:

https://youtu.be/2kxanBYTAaY

TL;DR - seems like the hot staging kicked the booster out in the wrong direction, and the ship’s plume impacted one of the grid fins, which would’ve given it quite a big kick. The sloshing just from that could easily have caused the observed issues.

Details/summary had quirky/inconsistent handling by screen readers for quite a while after it reached full browser adoption, unfortunately. Not even sure if they’ve fixed it here in 2026, honestly.

https://www.scottohara.me/blog/2022/09/12/details-summary.ht...

While it’s good to use well-implemented semantic elements when possible, there are still plenty of places where either the built-in browser behavior isn’t actually very accessible (like native form validation), or where you just can’t avoid it (using aria-disabled instead of disabled for submit buttons, setting aria-pressed for toggle switches, setting aria-expanded for buttons that trigger modals, situations where you need aria-hidden/sr-only, etc).

Though once popovers and the invoker command api hit baseline widely available, we’ll be able to drop some of that.

This is nonsense, you can stick classes on semantic HTML elements just as easily as on a div.

And screen readers can handle elements nested inside a grouping div just fine, that’s how div’s are supposed to be used. The accessibility issues with div’s are when people repurpose them to take the place of existing semantic elements, because doing so requires handling a bunch of aria roles and attributes manually, and something invariably gets missed.

This is not true. Tailwind defaults to rem as the underlying length unit for almost everything. You have to go to extra effort in most cases to use px.