All 9,300 Japanese train station, animated by the year it opened (1872–2026)

I hate the History API especially pushState. Even with this limit of 100 times per 10 seconds it still pollutes my browsing history too much. I need to vibe code an extension that makes pushState/replaceState noops on all webpages.

I've had some luck giving either an example website to ape or listing out a particular era, monkey see monkey do seems to help a bunch.

I've done each of the 3 for side projects below to pretty good effects.

> This website will be run by IE6 and Windows Mobile 6, so use no dependencies, semantic HTML, a 3-pane layout, and only use JS (es3!) where absolutely necessary (and where necessary, put the script at the end of the body).

When I'm not specifically targeting support for retrocomputers I do something like this, then iterate until it looks right.

> Go look at Dokuwiki, django defaults, and common web 2.0 color schemes, use those for UI inspiration. Keep a 3-pane desktop-first layout, but enable mobile responsiveness with media queries. Use semantic html5 and prefer older boring solutions like surgical jquery or htmx-style islands of interactivity where needed, otherwise do not bring in dependencies without my say so.

And finally, if I'm doing a web app that I'm vibing out with the web stack because I want it one-shotted and not trying to do a good rust core with strong ports/adapters API surface for web or native client callers, I do something like this:

> This is a local web app, the frontend, backend, and desktop are all on the same machine. Use naive and simple development patterns that you document the style as you go, pick a boring web framework and use it idiomatically, but remember that some tricks that are intended to keep network round trips down are not as necessary because network penalties are not as bad as real traffic.

Granted, the above I don't like as much, but it does produce more 'modern' looking sites by default.

Not sure that's necessarily any bigger a deal than when every Web site had the "Bootstrap look."

Anthropic's own frontend-design skill attempts to do that. You can install it in Claude Code, or you can tweak it to be closer to your own style:

https://github.com/anthropics/claude-code/blob/main/plugins/...

But what I find works best is to point Claude at a design system documentation website (your own company's or another public source) and tell it to use that design style. It usually does OK, and the results are usually much more in line with that style and not as Claude-y.

Just give it actual ideas of what you want instead of "make me a web page". Garbage in garbage out.

I get the sentiment. I don't love that different browsers have different behavior even on standards compliant code. But I've also done enough web development to know that if your page crashes safari in the main user flow (in this case, just hitting 'play'), the dev owns the bug.

Safari didn't crash. The web app did, for abusing the browser history API.

> SecurityError: Attempt to use history.replaceState() more than 100 times per 10 seconds

>people getting wealthier and buying cars

Haha, my experience is people buying cars feel poorer, not wealthier. Car payments, maintenance, insurance, taxes, fuel... and as soon as you finish paying it off, it's basically EOL. Time to start paying for the next one.

The "decline" you mention is privatization of JR and their efforts to make it more profitable. Privatization started in 1987, but it wasn't fully privatized until 2006.

If it has anything to do with babies, you have your cause and effect reversed. Autos are a cause of declining birth rates...

https://www.journals.uchicago.edu/doi/10.1086/731812

So a reduction in trains causes a reduction in birth rates, not the other way around.