Nmn

The Suicide Squad (2021)
dir. James Gunn

This is a common feature across agents. Codex, Claude Code, Open Code all have context summarisation built-in. Except you can just keep going in the same change from UX perspective.

Do you have links to sources about Kamala and Walz’ statements?

I also know about Schumer and Jeffries…

Cursor is an editor first. Everything else is built on it being VS Code at its core. But if they screw up that part the rest of it crumbles.

Yup but looks like it’s still available standalone.

ESLint plugin not working. Random freezes and UI glitches. Integrated Terminal randomly scrolling all the way to the top for now reason.

And there’s the new “features” that just get in the way that I have to spend time finding ways to turn off.

The way the agent panel will re-open every time.

The fact that Ladybird abandoned Swift and went to Rust is a huge fail for the interop story for Swift.

Swift was supposed to have first class C++ interop. What happened?

We need better tooling. And more polish. Let’s put moratorium on new features.

I would keep paying for cursor even if all it got me was the next edit predictions.

But

It has gotten so buggy it’s basically unusable. So I cancelled it.

Maybe Ill try Supermaven

I would keep paying for cursor even if all it got me was the next edit predictions.

But

It has gotten so buggy it’s basically unusable. So I cancelled it.

Updating the mailing list and website are too hard. And that’s the entire answer.

Wrapping react-query APIs is one of the most painful things I’ve done. Worth it though.

Should start a sequel to css-tricks called css-rants but it’s only shorts like this!

team i'm FIRED UP about these gnarly gotchas with Anchor Positioning in CSS.

Color Game — How Well Can You Remember Colors? We show you colors. You recreate them from memory. Challenge friends to beat your score. It's harder than you think. Play free at dialed.gg.

My color memory is a 42.8/50. Please do worse so I feel better.
dialed.gg?c=XSZ6PZ

I got between 8 and 9 on everything.

The most common complaint about themes in StyleX and I’m tired of explaining to people that this is just how CSS variables work!

A) shadow dom considered harmful

Truer words haven’t been said. Also sho king to me that more languages don’t have alternative syntax options. Think Reason for OCaml, Coffeescript for JS (even if I hated that syntax).

Where’s the rust but descriptive words instead of inscrutable symbols for everything?

Also, aliases.

if syntax truly doesn't matter... then why not give the people what they want? since it doesn't matter anyway

compiler people love to complain that users only care about syntax... but syntax is the primary affordance that users use to interact with your tool! of course it's massively important what that syntax is!

Long interesting discussion about this.

True but then I don’t think it’s a “dialog” anymore. There are many patterns on webpages where functionally it’s just a “route” but we want it to look like a dialog for visual reasons. And there’s other exceptions where we want things that are like modal dialogs but not.

Popover that shit!

I agree about the problem with extension but I wouldn’t call it a chicken and egg problem.

There is nothing stopping the extensions from all moving to use popovers today and unblocking everything!

Just realized that if there are valid use-cases for modal dialogs that aren’t actually modal and we wants toasts etc, we should probably use popover for that. As the worst thing about the alternatives is the need for portalling.

Now that Scott has chimed in a feel a lot more confident about all the “issues” with the HTML dialog element also being issues for a11y.

You’re describing a “website in a website” pattern which I 💯 agree should exist but afaik, is not supported at all by wcag

Because essentially what you want is a “scoped” dialog and that’s not a pattern.

Maybe iframes?

That’s a toast within the dialog then. It shows up after the dialog and can work fine by using popover.

Unless that toast is about something in the dialog it’s probably breaking a11y guidelines.

Toasts can be built with popover so any toast within the dialog will work correctly.

It’s true that many designs want that but I’m pretty sure all of that is bad for a11y. A modal means not having access to any other content. Toasts should wait for the dialogue to close. Support chat widgets should become inert.

In anything but the absolute largest web apps I don’t think these edge cases matter. Where you can’t control the whole architecture.

At the same time I know that many website intentionally break the requirements of dialogs by putting things above it etc. So it’s not always viable.