USD is backed by the U.S. military force, via a slippery slope: you can only pay taxes in USD, and if the taxes you owe are large enough and you refuse to pay, the U.S. government will send increasingly larger forces to claim those taxes.
As long as the docker daemon starts on startup, there's a `restart: always` option in the docker-compose.yml config file that takes care of it. Using `depends_on: [list]` takes care of startup order cleanly.
I'd argue that this limitation is artificial as well. With some painting forgeries, you're getting down to the molecular or brushstroke level of differentiation. It's all about the value that we humans assign to what's considered "an original", and I think that's what's happening with NFTs today. Unlike tangible art, however, I think NFT art is much more volatile and prone to the Beanie Babies effect if its popularity wanes.
> what's considered "an original", and I think that's what's happening with NFTs today
An original what? Remove everything off-chain from the conversation. All you have left is a small amount text (which itself is *information* !!) in a distributed database. Thats no more original than the particular instance of bootloader code in my desktop computer.
I agree with you. Removing anything off-chain from the conversation, we're left with the equivalent of selling a million pixels on a web page (but at least there was some utility to that, in the form of advertising).
The (U.S.) dollar is backed by the U.S. Army and always will be. Confidence decreases? The U.S. will likely start a war with the country whose currency tries to replace it (on "national security" reasons).
In that scenario, trust shifts to somewhere the U.S. cannot easily regulate. In case of crypto, that can just be banned and rendered useless, as long as the rest of the world is USD-bound.
If a crypocurrency becomes popular in another country using another currency to on- and off-board, see my comment.
It would take a miracle for cryptocurrencies to suddenly replace fiat without being bound to any fiat currency. Essentially, all the world would need to switch trust at once.
Without Tailwind: guess at what the proper class name is, use it where you think it makes sense, eventually find out you got it wrong and have to fix everything.
With Tailwind: defer decisions about assigning classes until you've built enough to see what the proper abstractions are, then just refactor out the repeated utility classes. There's even plugins that will consistently sort your Tailwind classes so that refactoring can be automated by simple search and replace.
I Ctrl-F'ed for Twist, made by the team at Todoist, but couldn't find it.
It has a way to go, but I found it the right mix of persistent, long-form discussion and decision making using Threads, and sync communication using Messages. It's the best of both worlds, if you can educate a team to use it properly.
https://sunroof.withgoogle.com/