superlucky84

8 ms·

1.
by superlucky84 6mo ago
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, and hydration complexity. So this project is basically me as
2.
Show HN: StateSurface – server-owned state and NDJSON streaming for MPA pages(github.com)
1 points by superlucky84 6mo ago|1 comments
3.
by superlucky84 8mo ago
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 session magic. Curious how others here handle AI agent hand
4.
Show HN: Ctxbin – A deterministic CLI for reliable AI agent handoffs(github.com)
1 points by superlucky84 8mo ago|1 comments
5.
by superlucky84 9mo ago
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 abstractions like monads or effect systems.
6.
by superlucky84 9mo ago
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, and rules about staying inside the context across the who
7.
by superlucky84 9mo ago
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 the place, but to surface them as part of a single, explicit
8.
by superlucky84 9mo ago
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 budget pretty quickly. That’s why fp-pack is intentionally na
9.
by superlucky84 9mo ago
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 “effects where normal composition should stop”. In practice, that
10.
by superlucky84 9mo ago
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 matters, the intended solution is to use `pipeSideEffectStric
11.
by superlucky84 9mo ago
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 visible in the code, rather than hiding them in conditionals
12.
by superlucky84 9mo ago
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. It’s meant as an explicit early-exit signal in pipe-fi
13.
by superlucky84 9mo ago
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 in real-world TypeScript codebases.
14.
Show HN: FP-pack – Functional pipelines in TypeScript without monads(github.com)
14 points by superlucky84 9mo ago|16 comments
15.
Show HN: Generate HTML Elements Using HTM ("Hyperscript Tagged Markup") or JSX(github.com)
1 points by superlucky84 2y ago|0 comments
16.
Show HN: Lithent" JSX-based virtual DOM library for lightweight(github.com)
1 points by superlucky84 2y ago|0 comments
17.
by superlucky84 2y ago
The default mode is that values reactively respond, and it also provides a mode that allows for easy Flux-like architecture.
18.
Show HN:state-ref Universal state management lib that can be easily integrated(github.com)
1 points by superlucky84 2y ago|2 comments
19.
by superlucky84 2y ago
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 deeply structured data. It provides more direct and fine-graine
20.
by superlucky84 2y ago
looks good
21.
by superlucky84 3y ago
Look so good
22.
Introducing a useful image editor implemented as a JavaScript canvas(github.com)
2 points by superlucky84 8y ago|0 comments