HN user

moklick

795 karma

Creator of React Flow and Svelte Flow - https://xyflow.com

twitter: http://twitter.com/moklick

Posts105
Comments59
View on HN
github.com 6mo ago

Benchmark algorithms for resolving node overlaps in a flow

moklick
1pts0
xyflow.com 7mo ago

Benchmarking node collision algorithms for React/Svelte Flow

moklick
2pts0
github.com 11mo ago

Show HN: Strudel Flow, a pattern sequencer built with Strudel and React Flow

moklick
37pts8
svelteflow.dev 1y ago

Show HN: Svelte Flow 1.0 is out! Rewritten for Svelte 5

moklick
20pts1
www.xyflow.com 2y ago

Show HN: React Flow 12

moklick
3pts0
www.xyflow.com 2y ago

Why _Svelte_ Flow?

moklick
2pts0
svelteflow.dev 2y ago

Show HN: Svelte Flow – a library for creating node-based UIs

moklick
81pts17
github.com 2y ago

React Flow now has a sibling – Svelte Flow – all in one new xyflow org

moklick
2pts0
noclip.website 2y ago

Noclip – A digital museum of video game levels

moklick
18pts3
reactflow.dev 3y ago

Show HN: React Flow 11.5.0

moklick
1pts0
github.com 3y ago

Show HN: Simple Mind Map App

moklick
6pts4
reactflow.dev 3y ago

Build a mind map app from scratch with React Flow

moklick
3pts0
github.com 3y ago

React Flow 11.4.0 Release

moklick
1pts0
reactflow.dev 3y ago

React Flow 11.4.0

moklick
2pts0
en.wikipedia.org 3y ago

Havana Syndrome

moklick
1pts0
github.com 3y ago

Awesome Node-Based UIs

moklick
194pts68
github.com 3y ago

React Flow 11 – better a11y, better edges, new hooks and more

moklick
2pts0
reactflow.dev 3y ago

React Flow library major release

moklick
4pts0
reactflow.dev 4y ago

Show HN: New React Flow version with sub flow support

moklick
2pts2
moritzklack.com 4y ago

Coronavirus Cemetery – 3D Visualization of Covid-19 deaths

moklick
2pts0
datablocks.pro 5y ago

Show HN: A flow based data processing editor

moklick
188pts20
aeon.co 5y ago

What happens when pacifist soldiers search for peace in a war video game

moklick
2pts0
www.jamesyu.org 5y ago

GPT-3 scheduling hell simulation between two friends who will never meet up

moklick
2pts0
github.com 5y ago

Show HN: React Flow – library for creating node based editors and apps

moklick
224pts58
webkid.io 5y ago

Show HN: We built a node based editor for data wrangling

moklick
8pts3
yoninachmany.github.io 5y ago

NYC 3D pointillist map with point cloud data

moklick
3pts0
www.zeit.de 5y ago

Interactive tool visualizes how the coronavirus spreads indoors

moklick
4pts0
d3-discovery.net 5y ago

D3 Discovery – Searchable and filterable D3.js plugin catalogue

moklick
3pts0
shaderbooth.com 6y ago

Shaderbooth – interactive editor for making face filters with WebGL

moklick
3pts0
twitter.com 6y ago

Covid19 browser plugin uses face detection to draw masks on faces

moklick
1pts1

I think it depends if you are working on an app or on a library. In an app I would recommend to use Zustand or Jotai. If you prefer a Redux-like state management with a central store and actions to update it, go with Zustand, if you prefer a proxy-based atomic solution, go with Jotai. There might be situations in library code where it's useful to use React context but I would not use it in app code. It's too easy to use it wrong.