> Like, of course you can prevent all memory safety errors by using a garbage collector. That has been known since the 90s.
No, it's been known since GC was invented.
> In fact, there was a good two decades after Java released where all the research on memory safety just stopped, because the standard answer became "use a GC".
For homework: if you make homework results not count towards the final grade, then there's no reason to use an LLM - the point then just becomes to have practice problems and feedback on how well you are doing.
This is what my university (EPFL) was doing ~40 years ago. And yes, some students didn't bother with the homework, and mostly paid the price at the final exam...
The open source policy described above was in place 16 years ago (I went through it to continue working on some existing projects), and I doubt it was very new then.
Not intrinsically or commonly deadly. https://www.hopkinsmedicine.org/health/conditions-and-diseas... says "1 in 10 people will develop a pituitary adenoma in their lifetime" - pituitary adenomas is the more general class of these benign tumors, as the pituitary gland produces multiple hormones.
> Even unemployment, which is your top line, seems... fine?
The unemployment one is interesting because if you look at that graph, the universal pre-2022 pattern is basically a spike of unemployment during recessions followed by a gradual drop.
The recent pattern is a gradual increase.
I'm not a big fan of "numerical only / shape of graphs" analyses, but this does seem strange. Of course, the 2020 Covid spike is also unusual, so...
The bit about "Canon, Sony, and Nikon may have replaced Kodak for professionals" was entertainingly silly. AFAICT, Kodak cameras were never used by a significant fraction of professional photographers? (maybe pre-WW2?)
> In my experience, when one begins to program in Prolog, they pepper their code with cuts to try and stop unwanted bactracking, which can often be avoided by understanding why Prolog is backtracking in the first place.
This gets to the heart of my problem with Prolog: it's sold as if it's logic programming - just write your first-order predicate logic and we'll solve it. But then to actually use it you have to understand how it's executed - "understanding why Prolog is backtracking in the first place".
At that point, I would just prefer a regular imperative programming language, where understanding how it's executed is really straightforward, combined with some nice unification library and maybe a backtracking library that I can use explicitly when they are the appropriate tools.
Conveniently, for individual sports like tennis there's a guaranteed renewal mechanism - the near-term likelihood of 50 year old tennis champions is low, and that of 80 year old champions is not really worth discussing.
> Quite the opposite. The benefits of rent control grow the longer you are in the same apartment without moving as the difference between what the tenant pays and the
You're assuming a form of rent control where new tenants pay market rate. That's not the only form, e.g., Berkeley's rent control used to continue "forever", until California forbade that (Costa Hawkins act in 1995).
No, it's been known since GC was invented.
> In fact, there was a good two decades after Java released where all the research on memory safety just stopped, because the standard answer became "use a GC".
Having done all of my research on memory safety after Java was released, I find this statement a little exaggerated... (e.g., https://barnowl.org/research/pubs/98-pldi-regions.pdf, https://barnowl.org/research/pubs/07-hotos-linux.pdf)