I would suggest you read the Gates report. I'm not sure how much to engage here, except to say emphatically that Gates said nothing of the sort. TL;DR - health and development funding should be considered as a more marginally impactful form of foreign and domestic government investment, but only because of the rapid (and ongoing) progress already seen in emissions reduction.
Here's a quote:
> To be clear: Climate change is a very important problem. It needs to be solved, along with other problems like malaria and malnutrition. Every tenth of a degree of heating that we prevent is hugely beneficial because a stable climate makes it easier to improve people’s lives.
Reducing sprawl is plainly a good strategy to reduce transportation and infrastructure needs, and preserve wildlife.
To me, this article demonstrated the value of knowing your domain and its particular constraints, as well as a good understanding of prior art. Together with the only 1000 line demo it took to produce (which I suppose could have been aided by an LLM), I did not finish reading with any specific appreciation for AI.
I highlight as a way to categorize my annotations. I highlight in Zotero as I go, and in the highlight's comment section briefly jot down why (e.g. something to follow up on, or whether this reminded me of something else it contrasts with). I dedicate a certain colour to "background references I should have", another to ~ "things I disagree with" etc., which I find useful when coming back over the paper to type up my notes.
In a sense the highlighting is just a way to localize my thoughts to a particular passage of the text, and the colours (or even highlighting at all) are secondary.
There's some considerable duplication of effort (notes in Zotero, then I type up notes in Obsidian, then also extract out some of those ideas into their own files). But, much like the recent posts about "outsourcing thinking" and GP noting that people sometimes do nothing with their highlights, I find that the work is useful for understanding and remembering.
Out of interest, why have you been considering Logseq?
It does seem to depend highly on the context in which the array is used. Strictly defined algorithm with an off-by-one: bug. User-defined indexing as you say is a counter. I suppose it is hinging on arrays being used in less dynamic contexts where you're likely to know the length, so to save you from handling all the Nones. I think I'd prefer a parallel api that returns Option, so you don't need to duplicate the bounds checking.
Just looking at the language myself, but it seems that it treats out-of-bounds array access as a non-recoverable bug and panics [1, 2], whilst map access returns Option [3]. Exceptions are a language construct only to enable Java compatibility and not recommended otherwise [4], but that's not to say you couldn't implement your own try/catch using the effect system. `r` is a region variable as the sibling comment says.
Here's a quote:
> To be clear: Climate change is a very important problem. It needs to be solved, along with other problems like malaria and malnutrition. Every tenth of a degree of heating that we prevent is hugely beneficial because a stable climate makes it easier to improve people’s lives.
Reducing sprawl is plainly a good strategy to reduce transportation and infrastructure needs, and preserve wildlife.