Live data from Hacker News

Useful patterns for building HTML tools

simonwillison.net

91–100 of 101 posts

Re: Useful patterns for building HTML tools

#91

Thanks Simon! My tool collection [0] is inspired by yours, with a handful of differences. I'm only at 53 tools at the moment. What I did differently: Hosted on Cloudflare Pages. This gives you preview URLs for pull requests out the box. This might be possible with Github Pages but I haven't checked. I've used Vercel for similar projects in the past. Cloudflare seems to have the odd failed build that needs a kick from…

> "I'm only at 53 tools at the moment."

Sorry if this sounds overly critical, but what do you mean "only at 53 tools?" Was there a memo I missed about a competition to host LLM-built tools?

Re: Useful patterns for building HTML tools

#92
post #55
post #52

I've been calling these Single-File Web Apps. I've written a couple myself: ≈ https://fuzzygraph.com ≈ https://hypervault.github.io/

Slight correction: I'd only refer to it as a "Single-File Web App" if it has no external dependencies (where as the "HTML Tool" definition allows for external dependencies loaded from CDNs).

I wouldn't call either of these tools that either. Using View Source reveals that there's a pretty obvious build step and confronts you with massive minified blobs. There's no way a person is going to be able open that HTML as a "single file" in their text editor to pick up development where it was left off. (In that regard, the HTML tools in the linked post are closer to the definition, even when they're written to load a module from a CDN.)

Re: Useful patterns for building HTML tools

#93
post #27
post #13

> The alternative to CDNs is to use npm and have a build step for your projects. I find this reduces my productivity at hacking on individual tools and makes it harder to self-host them. No. You can vendor these scripts & host them 1st party so you aren’t leaking data to these CDNs or risk users not actually getting the scripts. It isn’t like CDNs give you a performance boost anymore. https://httptoolkit.com/blog/pub…

I wish vendoring was less of a hassle. I'll vendor and self-host for my professional projects, but for these small experimental utilities I've stopped caring.

[deleted]

Re: Useful patterns for building HTML tools

#95

Thanks Simon! My tool collection [0] is inspired by yours, with a handful of differences. I'm only at 53 tools at the moment. What I did differently: Hosted on Cloudflare Pages. This gives you preview URLs for pull requests out the box. This might be possible with Github Pages but I haven't checked. I've used Vercel for similar projects in the past. Cloudflare seems to have the odd failed build that needs a kick from…

> "I'm only at 53 tools at the moment." Sorry if this sounds overly critical, but what do you mean "only at 53 tools?" Was there a memo I missed about a competition to host LLM-built tools?

Maybe you’re ignoring the context that he’s replying to the author and saying “only” because he’s comparing his 53 with the author’s 150+

Re: Useful patterns for building HTML tools

#96
post #19

Unrelated, but I bought a walking pad, and because I often use it at home while working on the laptop, and I wanted a nice UI to track the speed/time etc, I just asked claude to do one: https://pastebin.com/5HRLh1G6 it does something like this https://imgur.com/a/888BtpG and connects through BLE

This does bluetooth? wow.

Re: Useful patterns for building HTML tools

#98

Earlier quoted context omitted.

> "I'm only at 53 tools at the moment." Sorry if this sounds overly critical, but what do you mean "only at 53 tools?" Was there a memo I missed about a competition to host LLM-built tools?

Maybe you’re ignoring the context that he’s replying to the author and saying “only” because he’s comparing his 53 with the author’s 150+

I read the article, and I saw Simon's note about the 150+ HTML apps, I just don't get it.

Re: Useful patterns for building HTML tools

#99

Earlier quoted context omitted.

Maybe you’re ignoring the context that he’s replying to the author and saying “only” because he’s comparing his 53 with the author’s 150+

I read the article, and I saw Simon's note about the 150+ HTML apps, I just don't get it.

There’s nothing to really get. There’s no deep meaning to the numbers or the comparison
Post reply on HN