pull down to refresh
Very useful insights & passages.
It’s easy to be gloomy about China today, given the obvious challenges with economic growth and authoritarian tightening. But I found myself more optimistic about the future while I was in Thailand. Some people are drifting away from China, and many of those who stay are dreaming of better futures. These are creative acts.
A recent Chinese blockbuster made Thailand appear to be a dangerous place to visit, and state media has occasionally amplified that sentiment. To Chinese and other foreigners living in Thailand, it’s absurd to think that crime and danger lurk around every corner because it’s a pretty safe place. They fear that state media is trying to create a pretext to justify a presence for Chinese police in Thailand, rather like how they are sometimes reaching into Mongolia.
Much of China’s present strength rests on manufacturing leadership. If China can’t achieve reasonably high levels of growth, then the manufacturing advantage will dissipate faster, along with many of its other capabilities. And Xi Jinping has formally de-prioritized economic growth as China’s top task.
If we obsessed only over America’s problems, it would be a pretty ugly picture as well.
Essentially it appears to confirm that both great superpowers are turning inwards to shrink the pie rather than looking outwards to grow it.
Definitely a very talented writer, with a knack for compelling stories, hooks & observations. Much more there than the above, but a very worthwhile read. Thanks for sharing!
LSP > ease of use > non-custodial adoption.
We see that already with Mutiny, Zeus and others implementing LSPs.
To add some must check sources about LNbits:
I have become a Go maxi.
After a long time working with Python and NodeJS software and after the initial weirdness (wtf are channels and goroutines and why should I care), it's feels really nice to work in a statically typed language (without generics however ...) again where concurrency support is built-in with goroutines and channels. It feels soooo much better to have a compiler do type checking for you (in a guaranteed way) even if that means you have to define your types first, so you are slower first. But I would trade runtime errors with compile-time errors any time.
Also, the build process spits out a single binary which can be run anywhere where golang is installed (afaik) and the ecosystem is not a complete mess like Python (looking at you, Python package managers) and NodeJS (npm vs. yarn, CJS vs ESM, Javascript vs TypeScript). I also like how imports work in Go. In Python, you run into this circular import issue pretty fast if you don't try to stay ahead of it.
I also tried to learn Rust but the syntax felt rough. When I tried out Golang, I didn't look back.
@theindranetworkprotocol also made me try out Go. If I remember correctly, he also mentioned here and there how awesome Go is.
Seeing things I want fast.
Without a doubt Damus. Even though there isn't an algo and I still have to sift through the noisy posters that I follow, at least I don't have to wait for everything to load.
I use damus on mobile, snort on desktop, but then I use iris for notifications because notifications are slow/unreliable on snort for some reason.
Less but it's mostly because there's no way to outsource signal discovery on nostr yet.
All of that said, I'm still very excited about nostr and everything that people are building. It's fun! It's also the best thing we've got right now. And everyone willing to speak on the matter seems to think none of these things I've listed are concerns/things nostr needs. So perhaps I'm wrong.