It's not HTML purism. It's simply recognizing that HTML and CSS have evolved a lot and many things don't need (or are close to not need) JS anymore. This shouldn't be taken as an anti-JS article, everyone benefits from these gradial improvements. Especially our users who can now get a uniform experience.

This article compares a single ChatGPT query against 1h of video streaming. Not apple to apple comparison if you ask me.

Using Claude Code during an hour would be more realistic if they really wanted to compare with video streaming. The reality is far less appealing.

Consider how many folks use Claude Code for an hour vs. streaming many hours. Globally, not among HN readers.

My bad, in the context of the article you are definitely right.

I think I was biased by the fact that this argument was used in an HN comment where people tend to be heavy users of LLM based agents.

You can type Option+Enter. A more standard Shift+Enter would have been better but until then that's the best we have

Looks like it's OpenAI response to Google's Agent Payment Protocol (AP2) but without the micro transaction part.

Do you mind telling us a bit more? I never used OpenCode, what makes it better in your opinion?

I'm consistently hitting weird bugs with opencode, like escape codes not being handled correctly so the tui output looks awful, or it hanging on the first startup. Maybe after they migrate to opentui it'll be better

I do like the model selection with opencode though

- opensource with an SDK so you can build things on top of

- supports every LLM provider under the sun, including Anthropic

- has built-in LSP support https://opencode.ai/docs/lsp

There's a bit of UI around it where you can accept the plan. I personally stopped using it and instead moved to a workflow where I simply ask it to write the plan in a file. It's much easier to edit and improve this way.

Yeah, I just have it generate PRDs/high-level plans, then break it down into cards in "Kanban.md" (a bunch of headers like "Backlog," "In-Progress", etc).

To be honest, Claude is not great about moving cards when it's done with a task, but this workflow is very helpful for getting it back on track if I need to exit a session for any reason.

i've experienced the same thing. usually i try to set up or have it set up a milestone/phase approach to an implementation with checklists (markdown style) but it's 50/50 if it marks them automatically upon completion.

I have this in my CLAUDE.md and it works better than 50/50. Still not 100% though:

### Development Process

All work must be done via TODO.md. If the file is empty, then we need to write our next todo list.

When TODO.md is populated:

1. Read the entire TODO.md file first 2. Work through tasks in the exact order listed 3. Reference specific TODO.md sections when reporting progress 4. Mark progress by checking off todos in the file 5. Never abbreviate, summarize, or reinterpret TODO.md tasks

A TODO file is done when every box has been checked off due to completion of the associated task.

I'm wondering if it's not just: spawn multiple time the same prompt and take the best

It is exactly that

Traefik maintainer here.

A significant portion of TraefikLabs' engineering team and maintainers are French. Before each new release, the team holds polls and spirited debates to determine which cheese would be the perfect fit for the version name.

Staying true to French culinary tradition, the enterprise versions are given wine codenames, with each wine carefully selected to pair perfectly with its corresponding cheese release.

Traefik maintainer here.

You are right, Traefik is fundamentally built around the concept of "providers," which are external systems from which Traefik obtains routing configuration and service/server definitions.

These providers can range from dynamic service discovery systems (like Docker, Kubernetes, Consul) to static configuration sources (file-based configs, HTTP APIs, etc.). The provider architecture is what makes Traefik particularly well-suited for containerized and cloud-native environments where services are ephemeral and discovery is crucial.

Traefik maintainer here.

Traefik is a reverse proxy and load balancer that automatically discovers services and configures routing rules dynamically through integration with various configuration sources such as container orchestrators (Docker, K8s, Nomad, Consul, ECS, ...)

As of today, Traefik is not a web server.