If you get hit by a blue shell with a build fully optimized for speed at the cost of acceleration, it's likely to cost you the race.
10 karma · joined February 13, 2025
If you get hit by a blue shell with a build fully optimized for speed at the cost of acceleration, it's likely to cost you the race.
When I'm deciding what tool to use, my question is "does this need AI?", not "could AI solve this?" There's plenty of cases where its hard to write a deterministic script to do something, but if there is a deterministic option, why would you choose something that might give you the wrong answer? It's also more expensive.
The jq script or other script that an LLM generates is way easier to spot check than the output if you ask it to transform the data directly, and you can reuse it.
I guess the goal for both is to give the user a chance to get out of autopilot, and avoid up-arrowing and re-executing.
The CDN approach works, but I don't love depending on some third-party service just so your app continues working. Instead, I like using vite with vite-plugin-singlefile. This lets you package your JS and CSS into a single HTML: https://www.npmjs.com/package/vite-plugin-singlefile
I notice, for example, that this doesn't include a <!DOCTYPE html> at the top, but it still functions because browsers accommodate incorrectly formatted HTML.