Ethereum

gm, hooks-based react evm rpc api was a terrible mistake

instead of having easy-to-follow top-to-bottom left-to-right syntax we have something similar to try/catch we had with promises when your eyes constantly search for state variables

looking at you viem

cto @ bwl.gg (lunchbreak.com), 80M+ users (bdut.ch) 🙏 built @remindme, @mintit, @gpt, @healthbot, farcantasy.xyz

not really sure what you mean, viem doesn't have hooks ser

still not sure what you mean, can you elaborate? 🫡

how would you achieve: caching, request deduplication, persistence, deterministic states, etc without imperative APIs?

think this is a critique on react hooks instead of wagmi tbh...

RSC + Suspense does solve this, and you can use @wagmi/core with that :)

hooks-based api for contract interactions makes it impossible to write easy-to-read stateful code of any real-world feasible complexity

it has to be a simple await statement, we shouldn't need three variables for return data, call function, and error — and then having to handle it in UI