davidkunz

I read it as "Turbo Hascal"

I'm afraid the performance won't be great. Definitely needs a caching layer.

Great, now please standardize the skills folder and the MCP config.

You are correct. I miss the time when OpenAI was open.

This is historic. For the first time, an open-weights LLM is right at the top.

We won't be able to run this ourselves, but many providers can.

Maybe they're animalsonvehiclesmaxxing.

I'm not an expert. Can't we abuse that LLMs don't need to receive audio as a continuous stream without interruptions? Couldn't we just send data and pipe it into the LLM with deduplication (if resending happens)?

  x...y...y[dedup]...z

I would like if some of that functionality is extracted in CLI tools. Then every coding agent can use it.

I haven't tried Löve, but I somehow enjoyed reading through the README.md, no AI slop, just a natural writing style with tiny indictors showing the authors' enthusiasm in creating software.

We need Net Neutrality for LLMs.

Useful for tests with LLM interactions.

Oh, you should have a look at Pi then.

https://github.com/badlogic/pi-mono/tree/main/packages/codin...

It's still possible to let users already type from the beginning, just delay sending the characters until checks are complete. Hold them in memory until then.

Give it "a week or two"

Just use skills, which allow progressive disclosure of information.

Falling sand games always remind me of the game Clonk. As a kid, I enjoyed digging tunnels, flooding them with water, all physics based. Great times.

On the website[1] it says:

  .opencode/skills

[1]: https://opencode.ai/docs/skills/#place-files

The root cause should be fixed.

Please standardize the folder.

  .claude/skills
  .codex/skills
  .opencode/skills
  .github/skills

> It's in Java, but the lessons can be applied in every language.

I can only discourage anyone from applying Java patterns all over the place. One example in JavaScript: There was a functionality that required some parameters with default values. The plain solution would have been:

    function doStuff({ x = 9, y = 10 } = {}) {  ... }

Instead, they created a class with private properties and used the builder pattern to set them. Totally unnecessary.

In JavaScript, I love the `async` keyword as it's a good indicator that something goes over the wire.

One step closer to Skynet

What I would love:

- Everything locally stored in the repo: PRs, comments, issues, discussions, boards, ... - CLI first - Offline first (+ syncing) - A website for hosting/presentation

jj describe -m "Good luck, Steve!"

I have huge respect for Mitchell, it's impressive what he achieved.

I agree with all the points of this article and would like to add one: Have a quick feedback loop. For me, it's really motivating to be able to make a change and quickly see the results. Many problems just vanish or become tangible to solve when you playfully modify your source code and observe the effect.

It's all good, man!