Live data from Hacker News

Jeffgeerling.com has been migrated to Hugo

jeffgeerling.com

251–253 of 253 posts

Re: Jeffgeerling.com has been migrated to Hugo

#251
post #206

Earlier quoted context omitted.

Ha. Well, https://taoofmac.com was ported to Hy ( https://github.com/rcarmo/sushy ) in a week, then I eventually rewrote that in plain Python to do the current static site generator —- so I completely get it. I am now slowly rebuilding it in TypeScript/Bun and still finding a lot of LISP-isms, so it’s been a fun exercise and a reminder that we still don’t have a nice, fast, batteries-included LISP able to do HTML/XML…

Babashka now has a built-in markdown library. Babashka now also has a built-in HTML parsing library: Jsoup. Why does bb carry too much baggage? Because it has useful libraries like the above?

No, because of Graal.

Re: Jeffgeerling.com has been migrated to Hugo

#252
post #223

Earlier quoted context omitted.

Interesting attempt at bad faith discourse. Assuming 500 bytes of metadata + URL per blog post, a one megabyte index is enough for 2000 blog posts. As already mentioned, you don't generate search result pages, because client side Javascript has been a thing for several decades already. Your suggestion of converting markdown on every request also provides near zero value. Writing a minimal server backend is also way e…

I'm sorry, I find your post insulting. I wasn't engaging in bad faith discourse intentionally, but your assumption that I am - ironically - doesn't feel like appropriate etiquette here either. Despite that, I'll try answer sincerely. Your 1 megabyte index file has just added over 2 seconds to your page load time in 30 different countries based on average internet speeds in 2024. Chuck in some pictures, an external co…

> Your 1 megabyte index file has just added over 2 seconds to your page load time

It might not be intentional (I doubt), but your replies really read like bad faith discourse.

Re: Jeffgeerling.com has been migrated to Hugo

#253
post #247

Earlier quoted context omitted.

I agree, nothing is perfect, there's a time and place for everything - I just think the coverage and advocacy of SSGs is disproportionate to the number of places where they improve things. I'm going to summarise the discussions I've had in this topic in a post over the next few weeks and I'll post it here. Thanks for humouring and challenging me :) I still do feel there's something not quite right. Hopefully I'll be…

> They make the web worse for the world by tempting the developer to take the easier, less interactive route than what would have been taken in the pre-SSG world. If I didn't have the static site option though, I might not host a project at all because I don't want to have to deal with the maintenance burden. I haven't kept up but it would be nice if there were more options between a no-maintenance static site hostin…

> I haven't kept up but it would be nice if there were more options between a no-maintenance static site hosting, and a high-maintenance dynamic site.

This is essentially my position in fewer and less argumentative words, including the "I haven't kept up bit", really:)

Your last paragraph was also really thought provoking. I'm torn on that though. I agree it's an almost off-putting amount of time for anyone who wants a personal website to reinvent the wheel when the client browser could help.

The main issue with that for me is that browsers require organisations to build and maintain, so I think we should always be careful about removing responsibilities from website creators and giving it over to browsers.

I guess the SSG and the browser points are both freedom vs convenience type tradeoffs where everyone has their own personal preference. It's all Web stuff though, so we should probably try keep it all open, flexible and resilient IMO.

Post reply on HN