manxu

That’s the thought I always had: When I develop in Node, I stand on the shoulders of ten thousand microbes.

Haha touché, two peas in a pod.

It’s a real shame. Great framework but based on a single purpose language by a company known to drop projects on a whim. I loved to play with it, but I can’t imagine sinking a lot of dev hours into it, knowing it could just disappear.

Did you look at Pelican? I share the frustration with much of Hugo’s infrastructure: the template language is buggy and inscrutable, and the plugin architecture wanting.

I ended up with Hugo, but I considered Pelican. It uses standard Jinja templates, which I find much more rational (but it might just be me) and I recall there were plugins for a lot of things, including different source formats. The code is written in Python, so that even if there isn’t a plugin for a format you need, there probably is a Python library for it and it should be relatively easy to make it a plugin.

Crap, now I want to switch to Pelican…

Hugo watch mode (both server and build) does not produce accurate sites on change and is really meant for development. I find after a developing for a while, I have to kill the process and restart it and then things are “fresh”

From reading the documentation, I strongly have the impression that hugo focuses on being fast on re-render and that the idea is to build and deploy to public site each time there is a change. The big difference is probably whether to render locally and push the generated content, or to push the source markdown and render remotely (which I chose).

I ended up with Hugo, a git repository, and a cron job for the build. I write an article, check it in, the server picks up the git change and rebuilds the site. What I like about the setup is that the server only has the binaries hugo and git, and a shell script for the rebuild. Also, I write in Markdown, add media to the git repository, and articles are published soon after I check in without any remoting on my part.

I did look at WriteFreely after the setup, though. I find the minimalist design very beautiful. Didn’t switch to it, but may look at it again for another project. https://github.com/writefreely/writefreely

we traced the issue to a 15-year-old Git function with O(N²) complexity and fixed it with an algorithmic change, reducing backup times exponentially.

I feel like there is something wrong with this sentence.

I completely agree. Unless Google is forced to install more than one app store by default, or forced to have multiple app stores downloadable on Play Store, three is no realistic way to install a third party app store on a phone. In both cases, Google’s cooperation is required.

It’s so weird that we have to go through hoops and loops to get rid of this stuff! I was sick of my Android responding to a long press of the power button, meant to shut it down, with a Gemini prompt. Took me an hour to figure out I can’t get rid of the function, but I can switch back (for now) to old style Google Assistant.

If you have to force functionality down your users’ throat despite them not wanting it, you already lost. Gemini is Google’s Clippy, just less iconic and more also-ran.