tuplates-py

Most of my web projects these days are vanilla. I'd been dabbling on simple things for years, but it took a big leap a few months ago when I discovered Web Components are still a thing and have come a long way since 2012. We're finishing up re-writing an app at work that went from a ~17 dependency Vue app to a ~2 dependency (d3js) Web Component app. The codebase is a joy to work on. No more dependency hell. We don't even need npm. The code, as committed to git, will probably still run unmodified on browsers in 20 years. It's a great feeling. A few tips: * If you have a lot of JS files and want excellent performance you may still be able to skip a build step by leveraging `modulepreload` * If you want some typing while still running without a build step, you can use JSDoc to embed TypeScript annotations for your JS[0]. * If you really want

I've experimented[0] with something along these lines. The basic idea is that it's desirable to be able to reuse snippets/functions across projects, but you shouldn't need to go full left-pad. So basically you run tuplates.py on your project, it goes through all files and any line comment that includes "tuplate_start(URI)" it goes out and fetches the URI (local filesystem or HTTP supported), and replaces everything until it finds a line comment with "tuplate_end". Nice thing is it enables basic templating in any language, and instead of checking templates into source control, you're committing working code. Also combines really nicely with jsdelivr where you can import specific versions of files directly from GitHub. [0]: https://github.com/anderspitman/tuplates

>> If you clone my blog[1] (with submodules) you should be able to host it exactly as-is from the repo. > Who would want to do that? Future me. Actually just today in order to publish this post I had to re-learn how I had set up my dependencies, so I switched it to submodules so it won't be a problem again. > However if you want to optimize for subsequent page loads I suggest you do so without compromising your initial page load and completely without JavaScript by utilizing link prefetching [1] which is supported by all major browsers [2] except Safari. Believe me, I spent a torturous amount of time trying to achieve the same results with static HTML+prefetching/preloading. First off, Safari is a huge number of users. Plus you can't include HTML from HTML, so this requires a build step (though I've been experimenting with a new tool[0] f