web3 frontend dev is maddening. Spend yesterday and this morning learning to build a vanilla wagmi React app. Got it working, so I started looking at making it pretty. However, if I want to use something like RainbowKit in it, it completely breaks the entire app and none of the steps in the RainbowKit guide line up with how wagmi sets up the project. It's as if there's an assumption that you'll only ever start from scratch with these modules and, if you don't, you'd better just start over, I guess?

The aggressive component lock-in and lack of modular design is truly frustrating.

* higher rank in Tae Kwon Do than Vladimir Putin
* hobbies include finding new lows of dad jokes
* opinions are my own and I will DMCA anyone who copies them

It’s really bad. I always end up pulling teeth. I will say Privy + Viem/wagmi has been a pretty good combo for me in the past, but I miss the good ole days of window.ethereum. Hoping they come back in a way that simplifies the flows once more yet enables more functionality

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links

Having dabbled my toes in pure ethers.js, I think I like wagmi more. That's a low bar, though, I feel, in the same way I once preferred jQuery when I had to make things work in Internet Explorer 6.0.