pancsta

It was good to meet at wasm.io!

TinyGo doesnt have networking in WASI[0] and the WASM websocket module[1] was last updated 5 years ago. Go without stdlib is not Go.

[0] https://github.com/tinygo-org/tinygo/issues/4880

[1] https://github.com/Nerzal/tinywebsocket

You need state oriented programming to handle that. I know, because I made one. The keyword is „unpredictability”. Embrace nondeterminism.

What if a search engine queried YOU? That’s the question (I guess).

Nice cheatsheet.

What’s AI?

Not DEX but android containers (termux, proot, chroot) and soon android Terminal. DEX is just an alt android UI, and the discussion is about desktop OSes, sooo…

Hybrid-coding, organic implies a complex cause-n-effect organism, not single a human with probabylistic search engine.

Youre just missing workflows (agentic code) by trying to outsource everything to the model. MCPs are not workflows…

WASM != JS (fortunately)

Does it WASM? Does it multiread? Bbolt does neither of these…

„Every website” == 6 websites. I like the table layout of the results tho.

Its laughable to think a corporation got inspired by this tiny extension for obvious chat features. Its just an overlap.

You should unslop your scroll, whats your strategy to fix half my viewport? I’ll tell you what it is - SLOP ;)

For pytoy - maybe. Me personally, would love LSP-sourced completion in jetbrains. This dump bot suggests compile errors, APIs sucked out of thin air and other model-sourced nonsense. It does NOT read my code as I read and navigate code.

Id like LSP LLM in my IDE…

> It captures the nondeterminism in the order of delivery of communications. The Subsequent transition captures fairness arising from the guarantee of delivery. We provide a denotational semantics for our minimal actor language in terms of the transition relations.

Juicy paper, not to mention the declassification. It really reminds me of asyncmachine.dev which has actors, relations, transitions, and embraces non-determinism.

AI automates deterministic tasks, in a non-deterministic way. Repetitiveness just gives you a pipeline.

And its in Go, so no package management joke involved. I will integrate it into my debugger, thx for the link!

It's the Go compiler, not LLVM (AFAIR). So greater compatibility, but only for ARM.

Workflow reproducibility with AI is tricky and needs an additional layer and a state machine. Im currently working on that, but for now all you can see is some tech demos and a bot https://ai-gents.work

Im curious, have you considered using tamago instead of tinygo? https://github.com/usbarmory/tamago

> tiny … language designed to be targeted by coding LLMs

so like Go?

> Key Features; Prefix Notation

wow

NEXT!

> I was a top 0.01%

wow

“Residential IP” sounds expensive though…

Lame.

You missed the point.

> Simply put, these companies have fallen for a confidence trick. They have built on centuries of received wisdom about the efficacy and reliability of computers, and have been drawn in by highly effective salespeople selling scarcely-believable technological wonders.

Calculators are ok, but LLMs are not calculators.

Not related really, as you can (and should) publish BREAKING.md separately. Release notes should inform more about new stuff than the update process. Usually PRs have details, so release notes can be easily automated. Migrations, on the other hand…

So like Ruby?

> To help, we're bringing Gmail into the Gemini era and making it your personal, proactive inbox assistant.

Who asked for help anyway? Gmail should be Gmail, continuity is not innovation.