jtolds
I did expect that this exercise would come after the first one though, and doing this on top of a solution to the first exercise is a bit harder. That said, I also don't mean to claim either are impossible. It's just tough to reason about.
As the author of the post, it's really gratifying to hear that this is your assessment nowadays. I agree, and while I'm not sure I had much to do with this turn of events (it probably would have happened with or without me), curbing the use of channels is precisely why I wrote the post. I felt like Go could be much better if everyone stopped messing around with them. So, hooray!
If you are intending to do something that has multiple concurrent tasks ongoing at the same time, I would definitely reach for Go (and maybe be very careful or skip entirely using channels). I also would reach for Go if you intend to work with a large group of other software engineers. Go is rigid; when I first started programming I thought I wanted maximum flexibility, but Go brings uniformity to a group of engineers' output in a way that makes the overall team much more productive IMO.
Basically, I think Go is the best choice for server-side or backend programming, with an even stronger case when you're working with a team.
So far, all data says that the climate scientists are dead on and have been very accurate: https://eps.harvard.edu/files/eps/files/hausfather_2020_eval...
What doom predictions from the last 20 years haven't come true? If someone says that doom hasn't happened yet, I guess what I want to say is that they haven't waited long enough.
I think the climate scientists are frustrated and giving up. https://www.nytimes.com/2022/03/01/climate/ipcc-climate-scie.... My initial link was an attempt to show where the Overton window is regarding the experts in this field, more than anything else. This comment is probably not the right place to bring someone up to speed with the climate science field when they can Google it themselves.
Without even going into the unsubstantiated assertion with #1, your comment on number 3 shows a dramatic misunderstanding of how compounding effects work. You can't use the last 20 years to linearly project like this. It is true that most scientists agree that humanity will likely not go completely extinct, but it is also true that most scientists agree that many, many individual humans will be impacted. It is tough to say just exactly how humans will be impacted, but think famine, war, major societal upheaval.
Here's a citation if it helps: https://academic.oup.com/bioscience/article/71/9/894/6325731
Lensm, a Tool for Viewing Disassembly
If you are looking to provide storage space to the network as a storage node operator, then your nearest reputable exchange should do the trick.
The platform roadmap is available here: https://github.com/orgs/storj/projects/23. Good question about Borg. We are supported by rclone natively, and I've seen some success with people combing Borg and rclone. But that's certainly something we can look into more.
In terms of "does the math work", you're absolutely right that charging $7/TB and paying $20/TB to our storage node operators is not sustainable. But it shouldn't be a surprise that this was an intentional early subsidy to grow the supply side of the network. In an open system like ours, you see these business dynamics, whereas you might just not see them otherwise.
To be fully transparent, we are working to reduce that subsidy now that we're hitting scale. You can see some of our conversations with our storage node operator community about this on our forum: https://forum.storj.io/t/announcement-changes-to-storj-node-.... You can also see full network stats here: http://stats.storjshare.io/
But yeah, I don't know how the Nix Foundation is getting their Fastly traffic paid for, maybe that's in/out of scope. Certainly they should keep Fastly if it makes the overall thing cheaper. Having a distributed origin (us) to dedicated edge cache (Fastly) makes for a strong distribution story.
> I'm very interested if you happen to know a cheaper alternative!
and
> Optimally you'd want a distributed CDN
https://www.storj.io/ is this thing!
I jumped on the Nix Foundation Matrix to try and help them directly, but for anyone reading this thread, Storj might be able to cut a zero off your storage costs. Check us out!
Full disclosure - I work for Storj.