More like “why the fuck would I walk all the way across the city now that I own a car”

That’s a bad analogy.

Using an LLM for coding gives you an initial speed up with the trade off being skill atrophy, and a build up of cognitive debt in the project.

A better analogy would be the Greek government before their national debt crisis. It would have been better to invest in themselves, not lie about their own finances, and not kick the can down the road. But they kept lying and kicking the can down the road because it was easier in the short term. Of course, we all know how that turned out in the end.

although I’m a little bit skeptical about having to integrate additional extensions and workflows

Just to allay your fears, it’s not a mishmash of random extensions and brittle workflows.

11ty was originally built in a more all-in-one box style, but it was kind of annoying to have 10+ templating languages to choose from (and all the dependencies that came along with them), when you only wanted one.

Every update, the author does two things:

1. Splits more functionality into first party plugins
2. Removes, or forks and takes over third party dependencies.

You can see that here: (data taken from here: https://www.11ty.dev/blog/dependency-watch/#full-history)

The first-party plugins are all compatible with each other and all use the same 11ty config with the same sensible defaults, and 11ty is built with all of the first-party plugins in mind.

You can add them all in if you still want the all-in-one-box approach, but this way lets your environments be smaller.

It’s basically pre-computed tree shaking.

There’s also a security argument for it. By splitting everything apart, you isolate security issues. If one of the random 10+ templating languages got a security issue (e.g. supply-chain attack, redos, misglobbing, etc…), it will only affect the projects that decided to use that templating language.

I haven’t used Hugo.

I went with 11ty a few years ago because I wanted to stay as close to the actual web standards as possible (so, HTML/CSS/JS).

The main reason why is that every additional abstraction layer and every invocation of “magic”, is just extra hidden complexity which makes things harder to debug, extend, and maintain.

Having a SSG in go/python/rust would have been an extra layer.

The “maintain” point above is something most others don’t think about until it comes back to bite them. Nothing is more frustrating than reopening a project that worked fine a few years ago, and even though you haven’t changed anything, nothing works, and when trying to update it you end up with Frankenstein’s monster.

11ty went out of it’s way to remain as simple as possible. Here’s your input directory, and here’s your output directory. That makes the maintenance and backwards compatibility really easy.

Then you can add the minimum required complexity/abstraction layers only when you need them.

In my case, I use:

• liquid template language, so I only have to write a layout once (header, footer, accessibility landmarks) and every page uses it by default.
• my own custom extension that adds the build time in a html comment for debugging purposes
• markdown (so content creator coworkers can create pages)
  • The project is set up in such a way where coworkers can write markdown in vscode, and see a live preview within vscode (using it’s own markdown renderer)

I’ll say the one thing I don’t like about 11ty is that it’s written in js, not ts. The author is all about simplicity and reducing layers of complexity. But now typescript has a typescript-lite version with the erasableSyntaxOnly flag, which basically allows it to run on node (deno and bun already ran typescript), so the next version (or one after), may be migrated to typescript.

The --self-extracting flag in deno compile --self-extracting looks awesome.

I could compile my 11ty stack into a single executable that I could send anywhere, but it would still be able to read external markdowns so semi-technical coworkers can make content changes without the maintenance overhead of a CMS and without the coworkers needing to learn modern web dev.

It would also be super awesome for all the internal tools I’ve built that need to run offline.

It’s going to be right next to Cavil Ave, the bar and club tourist road!

Just imagine all the schoolies and just tourists in general taking a shit on the front steps of any building with trump in the name.

There’s so many tourist drones flying every night, you’re going to get FPV drones launching bags of dog shit, buckets of paint, and spray painting giant cocks on the side of the building.

Gold Coast mayor says he looks forward to considering a ‘formal development application’

Maybe, maybe not.

Tom Tate has a history of being an utter whore for real estate developers.

He’d slather himself in horse diarrhea with a smile on his face if he thought it would get him a new bribe.

But an association with Trump might shock enough people to give him a hard chance to get re-elected.

So he’s probably considering if he can get a big enough bribe to retire so it doesn’t matter if he doesn’t get back in.