Viewing profile — superlucky84

A bit more context on why I built this: I like MPA simplicity, but I also wanted progressive in-page updates without turning everything into a SPA with client state, router logic, …

Hi HN, I built an experimental web runtime called StateSurface: https://github.com/superlucky84/state-surface https://state-surface.subtleflo.com/ It explores a simple idea: Server…

Built this after repeatedly losing context between multiple AI agents working on the same repo and branch. I wanted something boring, explicit, and repeatable — no hidden memory or…

Hi HN, I built ctxbin, a minimal CLI that lets AI agents reliably save and load shared context using branch-scoped keys inferred from git. The problem I kept hitting was that hando…

fp-pack is also intentionally scoped for everyday frontend developers. It tries to borrow function composition and declarative structure without requiring familiarity with full FP …

One more practical point is that a full monad doesn’t fit very naturally into a pipe-first interface. Once you commit to a real monad, you need map/flatMap, lifting, unwrapping, an…

I understand the concern. The intent isn’t to add more side effects to an already side-effectful language. It’s closer to the opposite: trying not to handle side effects all over t…

I really relate to that. There’s often a gap between what feels conceptually clean and what teams are actually willing to carry cognitively. Rx in particular tends to exceed that b…

Good question. Early termination is the most common use case, but it’s not the only thing SideEffect represents. The name is intentionally a bit broader — it’s meant to model “effe…

That’s a fair point — it can definitely become a footgun if you’re not careful. This happens because `runPipeResult` defaults its generic parameter to `R = any`. When type safety m…

That’s a fair point, and I agree. The SideEffect pattern is intentionally explicit, so without fp-pack context it can look unfamiliar at first. The trade-off is making early exits …

It’s definitely monad-adjacent. The main difference is that SideEffect isn’t a compositional context — there’s no bind/flatMap, and composition intentionally stops once it appears.…

One thing I’d especially like feedback on is the SideEffect approach. It’s intentionally not a monad, and I’m curious how others feel about this trade-off compared to Option/Either…

Hi HN, I built fp-pack, a small TypeScript functional utility library focused on pipe-first composition. The goal is to keep pipelines simple and readable, while still supporting e…

"Lithent" has implemented the bare minimum functionality needed to create and update virtual DOM in general (we only need to know 'render', 'mounter', 'updater', 'renewer', 'mountC…

The default mode is that values reactively respond, and it also provides a mode that allows for easy Flux-like architecture.

StateRef is a state management library focused on data immutability. It combines proxies and the functional programming lens pattern to efficiently and safely access and modify dee…

looks good

Look so good