I had a similar realization when I was at Google. Someone made the observation that if Google had a one-in-a-million error, that meant it was happening 50-60 times per second.
What happens when the last coin is mined and there's no incentive for people to run the network of computers that validates transactions? It seems like at that point the value would go to zero.
And yet it is (extremely) improbable that individuals will pay many many billions of dollars/year to move money around (which is what it takes to secure the network).
The only way the network's security does not collapse is if bitcoin's value goes up faster than it declines over time (50% every four years (the halving)).
No one does the basic napkin math on this and it drives me nuts. Unless the code changes, Bitcoin inevitably fails.
The financial industry is 20% of US GDP, and its sole purpose is "moving money around" (including forward in time, which Bitcoin isn't all that good at, but Ethereum is pretty effective for). That's about $5T that people pay.
You don't need the price to keep going up, if you have a permanent backlog of high fee paying transactions. Which is what the Bitcoin design is counting on...
"And yet it is (extremely) improbable that individuals will pay many many billions of dollars/year"
And yet it is happening right now ! You should have looked at the data to see what fees are being paid :-) Looking at the average over the last 10 days: bitcoin users have been paying about 1 BTC in fees per block, so 6 BTC of fees per hour, or $8M per day, or $3B per year (yes, billion with a B): https://www.blockchain.com/explorer/charts/transaction-fees-...
I can't locate a source that calculates exact fees spent over the last 12 months, but per the chart above it seems to be around $1B per year.
First off, thanks for doing something cool and releasing it as open source! Second, think the person 2 messages up has a valid point and I would like to offer the same constructive feedback.
As someone who is doing a lot of React/Tailwind development lately the more you can assemble larger pages from independently usable components the better. For example here: https://easyfrontend.com/components/ui/all/html?page=1
It would be useful sometimes to be able to search for a "card" component that I want to use rather than remember that I want to see cards I need to go to Blog #10. This seems to be my normal intent when I'm using a framework is that I'm trying to find a [card, dialog, select box, data table, etc].
Anyway though, don't let the feedback get you down, it's awesome and greatly appreciated that you're releasing nicely designed Tailwind UI components. Github repo starred and thread upvoted!
There are loads of those already. For chucking together something decent quickly we need more 'block' level components than elements.
I tried not to buy flowbite but it just speeds things up so much, it's a no-brainer. This is in a similar vein and will be ok for some less discerning use cases.
+1 to this sentiment. You'll also run into similar problems if you need to request quota increases. For companies that AWS takes seriously they'll approve the requests in a few minutes. For startups they'll literally take days reviewing the request before some random person at AWS decides whether to increase your limit or not.
Insurance companies are just legal scams. They take your premiums then come up with whatever excuses possible to avoid or delay paying out on legitimate claims.
reply