Content pfp
Content
@
0 reply
0 recast
0 reaction

borodutch pfp
borodutch
@warpcastadmin.eth
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
5 replies
0 recast
4 reactions

Syed Shah๐Ÿดโ€โ˜ ๏ธ๐ŸŒŠ pfp
Syed Shah๐Ÿดโ€โ˜ ๏ธ๐ŸŒŠ
@syed
Looking through? With my physical eyes? No ty, Iโ€™ll just wait for GPT5. No more coding like a barbarian. (Also idk what youโ€™re referencing here, just wanted to spread the good word of the return of our lord)
1 reply
0 recast
1 reaction

jxom  pfp
jxom
@jxom
not really sure what you mean, viem doesn't have hooks ser
1 reply
0 recast
0 reaction

awkweb pfp
awkweb
@awkweb
tell me you like imperative programming without telling me you like imperative programming (react is declarative btw)
1 reply
0 recast
0 reaction

Michael Anyi pfp
Michael Anyi
@michaelanyi
I was shocked to see the new hook based primitives. it has his benefits for native rpc calls but beyond that just adds unnecessary boilerplate to my code base
1 reply
0 recast
1 reaction

Jay Brower (jaymothy.eth) pfp
Jay Brower (jaymothy.eth)
@jayb
my main feedback on wagmi/viem isn't the hooks, it's the fact that you need a ph. d to read their types good luck trying to use viem without inferred types
2 replies
0 recast
0 reaction