If I had to pick just one reason to use Foundry over Hardhat, it would be that I don't brick my entire repo when I try to upgrade and my yarn.lock dependencies collectively all shit themselves.

I love the Typescript language, hate the JS development ecosystem.

helping others build with LLMs and ML | YC S22, CMU CS + LTI | I write technical posts for ML builders at http://dbmikus.com

Counterpoint: some of my Hardhat test code becomes my web app implementation code, so that's a +1 on the Hardhat side!

When you say “brick” are you referring to dependency trees, version bumps, etc. breaking? Like cannot resolve imports properly?

Or more that in JS ecosystem, APIs change relatively fast and folks don’t really adhere perfectly to semver, backwards compat, etc.

I’m not as experienced and trying to learn
(React a little)

But it’s interesting to hear the complaints of more experienced people