A lot of communication is just mentioning the concepts.

(As in: Kids discussing something "important" to them while the parents chuckle)

I like the do notation better because it expresses the intent at the point of usage and I don't have to look up the definition when coming back after a few weeks.

    def foo(bar, baz, womp): 

    foo(1, 2, 3)

    foo(bar=1, baz=2, womp=3)

An "infinite" canvas without some notion of recursion such as viewports feels incomplete.

Obsidian's implementation of JSON Canvas supports this.

It is a great VSCode extension as-is, but the maintainers have abandoned it and they keep refusing to make it open-source. Someone is bound to make an open-source copy soon.

The upside is that it does not leave the most important aspect open to interpretation.

But it prevents this from being text-only at the point of creation:

You'll most likely need some programmatic environment to create non-trivial diagrams.

But then the question is: Why not just an SVG instead?

Opus 4.5 is $25/m output tokens.

This is at most $6/m output tokens.

That's ~1/4 the price.

---

Personally, I'm still very interested in the topic.

But since the tech is moving very fast, the discussion is just very very unevenly distributed: There's lots of interesting things to say. But a lot of takes that were relevant 6 months ago are still being digested by most.

Never heard this and I like it very much. This is just an off-topic comment to say thanks!

I don't like the hype language applied by the channel host one bit - and so this is not something where I expect someone tired of the hype to be swayed - but I think his perspective is sometimes interesting (if you filter through the BS): He seems to get that the real challenge is not LLM quality but organisational integration: Tooling, harnesses, data access, etc, etc. And so in this department there's sometimes good input.

Commands to go specific microservices with local state persisted in a small DB; queries go to a global aggregation system.

This is not AI specific and nothing new and also precisely why microservices are a good solution to some problems: They reduce a teams cognitive load (if architected properly, caveats, team topologies, etc, etc)