Not to be confused with “human” thanks to SCOTUS.

Not unless they are marketing it as “autopilot” or some such that a random consumer would reasonably assume meant autopilot.

And I’d include “AI driver” as an example.

A random consumer doesn't actually understand what Autopilot means. Most people don't have pilot's licenses. And cars don't fly. Did you not see all the debacles around it when it first came out?

They say they will, but until relevant laws are updated, this is mostly contractual and not a change to legal liability. It is similar to how an insurance company takes responsibility for the way you operate your car.

If your local legal system does not absolve you from liability when operating an autonomous vehicle, you can still be sued, and Mercedes has no say in this… even though they could reimburse you.

No. They don’t. It was vaporware made to fool people including you. You could never actually order it and it’s canceled now in favor of an L2 system.

The cost side of that protection is < 0.1% not 30%.

This is true for the console in dev tools as well.

Problem there is you can’t change css so at the moment the systems color preference changes thing will look bad.

Important considerations for custom formatters.

Here is a screenshot for my personal example:

https://github.com/workglow-dev/workglow/blob/main/docs/deve...

Play with it here using dev tools (you can ignore the website itself): https://workglow-web.netlify.app/

Docs including útil for checking dark mode: https://github.com/workglow-dev/workglow/tree/main/packages/...

Why stop at the engine?

Why not? You can have bun or even node these days run it directly.

I've been using node for a decade now and I've had to update NPM libraries a number of times as Node itself upgraded. I have a feeling it will get a lot more stable with ESM and the maturity of the language but if you're writing something you need to run 5-10yrs from now I wouldn't touch a library unless it's simple and has few of it's own dependencies.

Deno has used ESM from the beginning and it’s required on jsr.io. I agree about avoiding dependencies, but maybe it’s okay if they’re locked to a specific version.

M1/M2 were pretty similar.

M3 had gigantic GPU changes.

M4 had some security stuff added, and M5 much more so. Not sure how/if those can be disabled. Others can be explain why this matters better than I can.

That’s not local though

Just have a new journal of only papers that have been reproduced, and include the reproduction papers.