Absolutely and I was thinking about this when I wrote my initial comment. It's a good consideration. Star Trek _does_ have an AI computer capable of generating code and stories and all it requires of the user is a little prompting.

TNG shows humans are using this technology to engage themselves. People rock climb, ski, perform Shakespeare. Holodeck authors are well-respected throughout the galaxy. They also warned us of holodeck psychosis.

Data is an android, but what about his story suggests we should slurp up doggerel? His existence is the pursuit of humanity's "essence."

The final season of Picard was pure fan service AND I LOVED EVERY MOMENT OF IT! Even when I'm critical of Trek, I'm still there and trying to enjoy. Thank you for sharing.

DSC and Picard were long slogs in the spirit of "grit" and "realism." SNW having fun, switching up the mood every episode, and telling stories is a breath of fresh air. Strange New Episodes! The Henson Studio collaboration was amazing. Since Netflix canned Dark Crystal, I've been missing my weird muppets traveling across time and space.

Both LD and SNW managed to get less of that Kurtzman stink compared to Academy, DSC, or the movie which shall never be named. I hope they'll let the franchise mellow until they find new direction. (And a new owner.)

* Lower Decks is the truest Trek to ever Trek, but I know that's asinine so I saved my opinion for the footnote.

* ENT was off to a good start, but the 9/11-ification of TV took it off course.

Two quotes from Star Trek "The Ultimate Computer" - a very prescient episode.

KIRK There are certain things men must do to remain men. Your computer would take that away.

---

BONES Compassion. That's the one thing no machine ever had. Maybe it's the one thing that keeps men ahead of them. Care to debate that, Spock?

SPOCK No, Doctor. I simply maintain that computers are more efficient than human beings, not better.

I've seen google STUN servers used in production. Folks probably rely on unpkg too much to deliver their JS. Good to consider these failure modes.

If your service runs on AWS, reaching amazon dot com seems somewhat more reasonable an internal health check.

At this point, what do the words even mean? Your own patience and available time are always completely random and fairly distributed across a large enough data set?

> Maybe I'd waste hours down the wrong rabbit holes trying to find a library that worked for my use case. Maybe I'd waste a day trying to get an API to do something it turned out it couldn't do. Maybe I'd have to redo my entire approach because of some factor I hadn't considered.

Our ignorance isn't random chance. As we research and experiment, we reduce the problem area.

I've also found that "bruh" and f-bombs get me better results, but like you say, I don't want to have that vocabulary.

- Always describe tasks in the positive. (Never describe tasks in the negative.)

- DO guide the user safely. DO NOT use DO NOT because the reader already DID.

- Give guided choices based on your expertise.

- Asking two-or-more questions results in one-or-less answers.

- Conditionals are also questions, so you only get one.

I only use AI agents and tools for work, I don't create them, so I'm not a subject matter expert. Where I've anthropomorphized the tools highlights my own misunderstandings.

I don’t want to necessarily argue about merit or quality, but I have seen that custom software can be accessible to a general audience.

How did you arrive at this conclusion? Are you actually the Big Bad Wolf? That sounds like something the Big Bad Wolf would say.

After initial page load, a service worker could intercept all the HTMX app's AJAX requests, but it could only work with what's already cached. Using a lot of tooling like workbox the developer could pre-cache the entire app. (Would that mean no dynamic responses?)

Alternatively, implement the entire HTMX app in JS, build the app once for the NodeJS/Deno backend and once for the front-end. After page load, the frontend could take over.

Or something like that. It's a bit convoluted as PWA solutions often are.

Because it’s a Microsoft product and Microsoft still follows Embrace, Extend, Extinguish process. Once every browser supports TS, what prevents Microsoft from revving TS with a license change? Who’s going to take over the TS fork?

This is a solid takeaway and applies to a lot of domains. Great observation