39 karma · joined May 10, 2018
On the one hand, it's really annoying when your client library doesn't actually support asyncio compatible code (ex libraries which perform synchronous network or disk reads/writes), and you have to wrap everything in an executor.
On the other hand, making it explicit ensures I'm actually doing things async. "Leaf" functions with an async containing no await is now a red flag to me.
It's a mental tax to remember that I may actually be returning a future instead of the result of a future (similar to how you can return a function but not the result of that function being executed, or a non materialized generator), and having to call 'await x' instead of just assigning x kind of violates 'do what I mean'. In the end, async is (relatively) difficult, so I appreciate the enforced explicitness.
The geographic isolation isn't as strong as the us', but it's much stronger than any other country in the region. Taiwan/japan/south korea off their border is the biggest issue
We're a long way from being Venus
I read your site, and it's all just FUD. You mention in passing how you'd need to grow agriculture to feed animals anyway, and then completely ignore that fact through the rest of your writing. You don't cite any actual environmental numbers, pull some out of your ass, and then hand wave your way through your position.
Also, with automated offense, a lot of people may die in short order if you encounter a systemic failure in your targeting + execution
If there's anything I've learned, it's that just because a language has a feature, doesn't mean it should be used.