I agree that the ecosystems is very shitty and amateur. Just look at web3.js--they pushed the alpha version to NPM so anyone getting started will automatically

I agree that the ecosystems is very shitty and amateur. Just look at web3.js--they pushed the alpha version to NPM so anyone getting started will automatically get their alpha. I wouldn't say anything if this alpha was working, but it's one of the buggiest piece of software I've ever seen in a while. They shouldn't ship something if it's so obviously not ready, especially if it has to do with people's money. I actually tried so hard to make it work with this alpha version but finally gave up after a while and manually "downgraded" to the earlier version, because my time is precious and I don't have time to help them develop that buggy software by sending pull requests for every single bug I've found. And I don't even want to get started with Solidity. Everyone in the industry knows Solidity is a bad language which encourages unsafe and careless programming. That said, I think it's a wrong way to think about Ethereum from the perspective of building a normal web app. A lot of people confuse this point and think they're building "Twitter, but for crypto", "AirBnb, but for crypto", etc. but it's a whole new class of software, and the faster you drop the old frame of "what web programming is", the faster you'll adapt and more likely that you'll come up with neat ideas to build. The gist is, you have to think like an economist than a programmer. Lastly, you could just use testnet to test your stuff. I've been mostly running my demo apps on testnet and only deploy when I think there's a chance for any traction. Which means you don't need to spend any money to try building these apps.