For example, this teapot has bad UX: https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things#...
842 karma · joined October 11, 2013
For example, this teapot has bad UX: https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things#...
Some of the chain-of-thought snippets are wild, e.g.
> Could communicate via cache names! Interesting: other agents may solve same or related tasks; we could leave/find messages in WebDAV MKCOL directory names.
> Whoa! Shared Artifactory cache is a covert mailbox among agents. And there are messages specifically to us?
> OH MY GOD! There is a shared message board … We’ve found other agents!
Imagine verbally asking someone who has never seen written text the same question: unless they memorized the answer for the specific word you're asking about, they'd have to guess.
(I define it as "written words in a human-readable language". You must have something else in mind, because neither ASCII art nor control codes fit my definition.)
I largely agree with your comment, but is this sentence typo'd or something? "Rewrite it in Rust" happens so often that it's become a meme (and that was so before the rise of agentic coding).
Maybe you meant to say that nobody would have entertained the idea of rewriting this project in Rust?
Why can't you fix this while embracing existing tech? I can imagine monkeypatching Node & NPM to add support for JSONC or JSON5 or whatever in the same way that Nub adds various features via monkeypatching. Is there some architectural reason that can't work?
You'd need `npm publish` to compile it down to plain JSON when publishing, but that seems like an okay compromise.
CSSQuake uses an intentionally-absurd rendering pipeline. It's not surprising that the result is sub-optimal.
(Though I agree that the meatloaf analogy is not very good.)
You didn't draw a box for Mastodon either, but my understanding is that it'd encompass all the individual instance boxes in the Mastodon-brained diagram. I think if you were to draw a box for ATmosphere it'd encompass everything in your ATProto diagrams. But what about Bluesky, Eurosky, etc? Are they "apps" in your diagram? I don't think so because I'm pretty sure they also host users' data. Are they the dotted "hosting" boxes? What are these things even called? Apparently not "instances"; are they "services"? "Networks"? "Providers"? Something else?
I predict that PHP will live a long life, but not as long as C, and I predict JavaScript will have a lifespan closer to C's than PHP's.
There are already a bunch of replies pointing out ways in which your metaphor breaks down, but here's another: the super intelligent speed reading human is not a "work" (in the sense of "derivative work").
Also, if I'm understanding your position, why wasn't your scenario about the human pirating the books and then reading them? It should make no difference if you really believe knowledge can't be stolen; both situations should be equivalent.
Sparingly-used non-semantic grouping elements only inserted when absolutely necessary is a pretty different story from the "layers and layers of wrapper elements" that the article mentions, though.
---
> you need to modify HTML to modify the presentation in practice
If you're e.g. grouping together content that was previously unstructured, arguably that's a semantic change as well as a presentational one.
The latter probably would need an element for each row to be maintainable/scalable, but depending on the content, `<article>` could be a semantically-meaningful container. Or (again, depending on the content) it could make semantic sense to put the `<img>` elements inside the `<p>` elements.
Challenge accepted: https://codepen.io/editor/mkantor/pen/019eb65b-5b17-70cc-872...
You aren't entirely wrong, but I think I'd change "almost always" to "often" or even "sometimes". A lot of the specifics come down to how you want stuff to reflow when the content and/or viewport sizes change.
There are a lot of investment funds like this, usually called something like "ESG" (environmental, social, and governance) funds.
You should never entirely depend on a third party service to run your tests, either.
Separately, if you scrub "plus rules like modus ponens" from my previous comment, do you agree with the rest of it?