Composability and open APIs are rarely talked about.
Composability lets you create a token to represent anything* of value and exchange it for other tokens. ETH and BTC are tokenizations of proof of work.
Open APIs exist for any verified contract on Ethereum. You can permissionlessly plug a new application into many existing ones if your application is even partially on-chain
+1 to this. Having nvim as my daily driver allowed me to NOT upgrade my 4 year old macbook with the next top-of-the-line macbook, saving me an arm and a leg. Instead I just got a gaming PC with way higher specs for less than half the price and I just ssh into it now.
It's also neat to be able to code from an iPad by SSH'ing with Termius :)
Coinbase is more about turning non-crypto currencies into crypto currencies while UNI/SUSHI are more about turning crypto currencies into different crypto currencies.
In my POV, there's only two ways to get into crypto:
- Centralized exchanges with KYC
- Mining
Coinbase is a KYC centralized exchange and enables people to turn their bank account $$s into crypto. Uniswap and Sushiswap are only relevant once someone has crypto and needs to exchange between various tokens.
> Sure, but why do we need a separate currency for all of this in the first place?
I might be answering the wrong q, but the separate currency represents the cost of a transaction in the network. I.e. the amount you're willing to pay to send a transaction in the network and the amount a staker is willing to receive in exchange for validating your transaction
How else would you represent that cost in a crypto network? Some kind of currency needs to represent the transaction cost.
Not sure if you've read up on recent developments in Ethereum, but in case you haven't, check out proof of stake [1]. Basically, POS lets people put their money on the line for consensus rather than let people only participate in consensus by solving hard computation problems.
I use vim as my main driver at work. Some things that helped me out personally:
- Playing some vimgolf and seeing what neat tricks people used. This is where I learned about “.”
- Going into the deep-end of just using vim (or just vim in IntelliJ without the mouse) will make you notice all the issues that make you unproductive with only vim e.g getting around with only hjkl is really slow so you might investigate other ways to navigate or deleting a word always involves getting to the end of the word and using lots of backspace may make you wonder if there are more efficient ways to do the same thing
- if you decide not to go into the deep-end, just being more picky about how much you’re spamming certain keys may help you gradually incorporate new commands into your flow
Also, this project ends up being a compact way to deliver educational material. Imagine sending them the equivalent in physical books and manuals