The early adopters will be the ones who reap the rewards.

Aave, Compound are both not Ponzi schemes and allow you to lock things like USDC and ETH (also not Ponzi schemes) for others to borrow, and earn interest. It's automated lending, I don't understand how people are not excited about this.

> Very rarely has any cryptographic algorithm been broken, but often one of the other links in the trust chain has broken.

The whole point of Ethereum is to reduce/eliminate those links in the trust chain.

How'd you get access to the API? When I tried it said it's full!

Cryptocurrency gets a bad rap here (most of it rightfully so), but one thing is for sure, once you use it you realize how broken digital payment infrastructure is. With crypto, I can trivially send any amount of money very cheaply across any sort of borders. Also, accepting crypto as a merchant is extremely easy even to roll your own custom solution.

Just recently started messing with AWS Amplify. It's crazy how easy it makes basically all this stuff. It really makes it simple to be a solo founder and manage every piece of the stack.

Interesting, one of the big reasons I want to learn Rust is to "future proof" myself once JS loses its monopoly on the web. Maybe Kotlin will be a better one than Rust?

Can you explain more about writing JS in an FP style? I'd love to start to incorporate more FP in my JS but I don't really know how to start doing that. I've looked at fp-ts but it seems like that would require a full rewrite. Any tips for how to basically start from 0 and start to implement FP into an existing JS/TS codebase?

I'd suggest just learning and applying fp principles in JS incrementally. You'll feel a bit constrained at first (in part b/c JS allows you to do many "dirty" things), but you'll end up writing better code. Try to rely on 1) pure functions/no side-effects: a functions return value should be completely determined by its input 2) immutability: no Array.push, pop, or any method that modifies its input values 3) recursion instead of for & while loops.

You'll probably feel the need for stronger typing at some point when adhering to these principles, and that's when I'd suggest looking at Typescript. By trying the things above you'll likely get familiar with the issues TS is trying to solve & you'll appreciate it more. Note that fp-ts is just a "helper" library for functional concepts, but it won't teach you their value or how to use them.

Also: many libraries have fp variations! Next time you reach for lodash, try lodash/fp instead: it has the same tools you'll already be familiar with, but implemented in a functional manner.

Yeah that's mind blowing to me. Lots of people think these ultra successful people are just immensely talented but overlook the insane amount of work they put in. My new theory for success is around obsession. If you find something that you can be completely and utterly obsessed with, that's how you can ultimately cultivate enough skill at it to be successful.

It seems like WebAssembly will allow high level languages to get close to the "browser metal", so I think we will see declarative frameworks that are closer to the metal compared to React. I'm wondering if Rust is the best language to learn to get a headstart on that.