Made a lot of progress on the web site today. I now fully support all the iTunes RSS features, even the ones we will probably never use. But they’ll be there for us if we need them.
Now to finish the RSS feeds I just have to add support for some other more general RSS tags that aren’t podcast-specific, and then add unit tests.
Other than RSS, the only other feature that should take me any significant time to code is the ETL from the current site to the new one. I estimate all the other features at a day or two each. Of course, there’s a very long list of them, so…
It’s questionable. I had to fight with it a bit at the beginning, but I basically have it setup where it just remotes into WSL and then is vim + terminals. I can avoid running some kind of X server this way.
The only IDE part of it that I actually use is the debugger. The Visual Studio debugger has always been the best even since the first time I used it in 1997/1998.
Looking very useful! Also, the first search took 0.011 seconds and the second search took 0.006 seconds. Effectively instant speed. Bonus, no ads, no tracking by Google, etc. Once this is live, nobody will have any problem digging through our old content.
I don’t know why the forum decided to color the first set of results…
I’ve been using HTMX lately in some stuff. It’s is pretty ok! And I’m saying this as a guy that thinks most js frontend websites are awful.
Instead of writing javascript, you put some attributes on your HTML tags. And this was the thing that got it over the hump for me - your backend just returns HTML, and htmx swaps the response in for the old content.
So you get interactivity in the old, least-bad sense of progressive enhancement. Without writing javascript.
For example, a user types a query in your search box, htmx POSTs that to the server, your backend returns a normal HTML response, htmx swaps the live-search results in.
Also it’s a single self-contained js file, so there’s no js build chain shenanigans. You’re not going to make something like google sheets with this, but it’s pretty slick for what it does!
This talk is a little loosey-goosey, but it gives you the idea. The amount of code you’d need with django is even less than flask here:
I’ve also been reading more about HTMX, Hotwire, and related tech. I haven’t tried it yet, but I’m liking it a lot in principle. Will definitely try it the next time I make a web app. Might even apply it to GeekNights web site in a future revision.
I was like, uh, Python already runs on all those platforms, but now I understand. They didn’t compile Python once per platform. They compiled a single binary that executes correctly on all those platforms. Impressive.