hckrnws

IMO the reset should fire regardless what happens after it.

Which I don't expect from the description, and I also don't expect from the code.

---

So outside of the simple "This is broken..." feedback, I want to further pick on this example:

Don't fucking hide the imports.

Especially don't fucking hide the imports if you're showing example code, and you're doing things like

```

import { Match as M, Schema as S } from 'effect'

import { m } from 'foldkit/message'

```

Which I only know because I bothered to dig through the example playground counter (which is a different example entirely!)

It's a huge issue to show demo code where concepts magically appear, and it's just bad manners to use shorthand at the same time.

a) Actually ship docs, and use AI to help (I also do a ton of hand editing and review cycles)

b) Have poor docs coverage because I’m handwriting everything

I’ve chosen A, but plan to do a few weeks of docs rewrites before I ship 1.0.0. I would rather it sound like me.

Cons: The API surface is huge so there is a steep learning curve.

The learning curve is steep tho.

In any case it's a hard technology to sell, you don't appreciate it from hello worlds. In fact you hate it for trivial programs.

It shows it's benefits at scale.

Lots of tools like T3 and opencode use it at their core because they solve non trivial problems made of queues, retries, dependency injection, schemas, etc.

I've written a vscode extension with it:

https://github.com/dearhuman/effect-decorate/blob/main/src/e...