Oh No! Is a much better name for error handling.

Cool! I had thought about doing the same but in a Chrome extension that would use Llama 3.2 with WebGPU, but when I tested it, it was very slow and sometimes crashed the browser.

Can't wait for physical paper with JS support

There is probably an E-Paper capable of JS support, however it would be difficult to use for printing due to it's thickness ...

https://en.wikipedia.org/wiki/Electronic_paper

I code and document code and imho Claude is superior, try to tell Gpt to draw a mermaid chart to explain a code flow... the mermaid generated will have syntax errors half of the time.

Yup, It's a shame that they're going to close the channel

Imho IDs are more explicit, and a bless when working with large codebase apps, when trying to finding the related code to an element just grab the id and search for it.

Exactly, and because they are specific for the purpose of testing they are less likely to break due to changes in the HTML.

perception != reality

There are reasons for why we can assume that the west is the least corrupt area of the whole world.

But for the average person, perception does influence how likely they are themselves to take part in corruption, and that in turn does influence the total amount of corruption in a country. Actual corruption is very hard to measure, so perception of corruption is a reasonable thing to research since it is in many ways "the best you can do" to get some measure of actual corruption.

Perception is a proxy for reality, given that you can’t measure the latter.

Prompt or it didn't happen

Hate to be that guy but "You need to enable JavaScript to run this app."

Yeah, it's not so nice once you browse past the landing page. You also have to enable cookies, or you'll get stuck looking at a pinwheel.

IMHO not a minor strength, getting pixel perfect designs when SVGs are involved in Figma is near impossible, they are rendered in a very different way and in some cases the differences are huge.