uhoh-itsmaciek

So what are you proposing? Force people to marry and have children? Ignore the problem?

Yeah, that was kind of ignored in the article and it's definitely an issue for some platform features. Date pickers are another one where it's easy to outgrow the native implementation.

So allowing projects like Nitter and XCancel must also be understandable, in order for recipients to be able to actually read these messages.

In Firefox, the page tells me neither my browser nor my display support HDR. In Chrome, it works fine. Latest browsers on a Pixel 8.

This doesn't really scale, and it doesn't really solve the problem for your (potential) users to wash your hands of software delivery like this.

Fair enough, but that move should make you think twice before tying your fate to theirs.

I ran into this problem recently on one of our blog posts: we used some Claude output which included tables drawn with Unicode line drawing characters. However, our monospace font did not include these characters, and so rendering fell back to another font in our font stack with different width metrics. I fixed it by using a font that had similar metrics and did include those characters with `unicode-range` (to only select characters we needed) and `size-adjust` (to match font width more exactly), and adding it to the stack. It's a little hacky but works pretty well in practice.

Another interesting related technology is electromechanical vane display clocks: https://youtu.be/AradTqh0cuM . Each segment is shown (or sometimes obscured) mechanically!

Could you elaborate?

Really nice explanation! One note: pg_repack is an extension, but Postgres 19 will get a built-in REPACK command: https://www.postgresql.org/docs/19/sql-repack.html .

Great point, but if the 2% are served graceful degradation rather than a broken site, that's probably okay.

Right. Backups don't matter. Restores matter.

HN submission titles don't need emoji.

>Without those periodic full page images in the log, the storage layer would have to replay an infinitely long chain of small deltas to reconstruct a page for a read request. What was once a bounded O(checkpoint frequency) replay becomes an unbounded chain, leading to a spike in read latency and resource consumption.

I don't follow: read requests are not served from the WAL. They read the current state of the page from the buffer cache, where the page is updated after the change (FPI or not) is written to the WAL.

You could prompt them through the material. But you're right, that's only gonna take you so far if you don't know where they're having problems.

>Kristen DiCerbo, the organization’s chief learning officer, said AI can only respond to students based on what they ask. And it turns out, she said, “Students aren’t great at asking questions well.”

Ignoring whether or not this is a good idea in the first place, what about inverting the loop? Have the robot drive the interaction.

That would be a really interesting platform for an npm alternative. I think the incentives are a little better aligned than in the WordPress ecosystem, but maybe not enough.

In text boxes in some applications, enter submits the entered text, and ctrl-enter forces a newline (not at my computer, but I think Slack does this). In others, it's the other way around (pretty sure GitHub does this for comments).

I don't know how we got here and I don't know how to fix it, but "bring back idiomatic design" doesn't help when we don't have enough idioms. I'm not even sure if those two behaviors are wrong to be inconsistent: you're probably more likely to want fancier formatting in a PR review comment than a chat message. But as a user, it's frustrating to have to keep track of which is which.

>The roads will be safer. The streets though? Remains to be seen…

What do you mean?

>Remove them from Unicode.

Do you honestly think this is a workable solution?

So it's basically GPLv3-or-later but with veto power of the "-or-later" part by the maintainer (but not the contributor). That's pretty clever. And, since you're asking someone to maintain your contribution, it also seems pretty fair.

The program with possibly my favorite error message: https://sourceforge.net/p/sbcl/sbcl/ci/master/tree/src/runti...

+1 for Foto. I was also using Instagram through a photography lens and fell off when it got totally unsuitable for that. Foto is pretty good so far.

No specific recommendations, sorry. Thanks for taking the feedback seriously, though, and good luck with finding a more reader-friendly platform.

Stop blogging on medium. I start to read your post and as I'm scrolling down the page, I get a full-page modal nagging me to subscribe. Why should I listen to anything you have to say about user experience?

The problem is having to look in a different file for styling a component, and having to come up with a name for (at least one) CSS class per component. In traditional CSS, classes are intended to be reusable. You write a class definition once, and then use it in a bunch of different elements.

When working with a component-based UI (like in React), the components are typically the unit of reuse. Those CSS classes are used in one place: the component they're defined for. It's annoying to have to come up with a name for them, and to have to work in a separate file, especially if I just want `padding-inline: 4px` or `display: flex`.

Some argue separation of concerns, but CSS is inherently tightly coupled to the structure of your HTML: there's no getting around that. `.foo > ul` breaks if you replace that `ul` child with an `ol`.

I do agree that more intricate styling is harder to read with Tailwind, and I have some other gripes, too, but in general it's a good trade-off for component-based UIs.

Josh Comeau's CSS course is excellent: https://css-for-js.dev/

Maybe a rounded border? I agree it's too subtle as is.

Also, your Segal's Law link seems to have an encoding issue with the apostrophe.

FF on Android seems to work fine here. What problem are you seeing?

This is reminiscent of the Homer: https://simpsons.fandom.com/wiki/The_Homer