There isn't any report that actually counts Gaza's population, the UN provided an "estimate" with no methodology, births are not mentioned, and it's built on figures including number of people who exited Gaza (irrelevant to the claimed decrease due to violent deaths). That's not serious.

There's no coherent notion of genocide that fails to reduce the population significantly. Yes, you can argue (and people have) that the legal definition, by using the "part of" wording, can conceivably apply to virtually any number of deaths, but again, that's not serious.

- the survey recorded a surprisingly small excess of nonviolent deaths (in excess of what's demographically expected), this is discussed in the preprint. The much larger number of violent deaths is almost matched by births, so the total balance is somewhat towards shrinking, in that cohort

- however, it is well known that the violent deaths occurred overwhelmingly early in the war (so far) - according to the official Hamas statistics, something like 50% of all casualties are in the first 4 months of the war, out of 22 so far. Whether these statistics are over- or under-counted is not likely to make a dent in this huge imbalance. So as the war is ongoing - and it's already been another 8 months since the 14 covered by the survey - the death rate is still "collapsing" compared to average rate so far.

- at the same time, the birth rate has evidently not seen such a huge collapse since the first 4 months of the war; this can't be gleaned from the survey, but enough plausible reports (e.g. what @richardfeynman quoted) exist that point in that direction.

So if we consider the survey relatively representative of the entire population, the imbalance towards shrinking population after 14 months is already almost certainly repaired towards growing after another 8 months, because so few civilians are violently killed (again, compared to the first 4 months of the war) in 2025.

Overall am in strong agreement with you, the main thing is to nail down data and very little seems to be done towards that. I've followed these studies and articles since 2011 or so with increasing dismay. The headline-grabbing stats of "1 in X" growing every year are next to meaningless, and yet I believe much points towards prevalence of actual condition really increasing. But with scandalously amorphous definitions and abysmal longitudinal bookkeeping we don't know and can't know how much it's increasing and in what subpopulations.

A recent study tries to define "profound autism" as "nonverbal, minimally verbal, or IQ<50". They found a significant increase in US children aged 8 from 2000-2016 with profound autism. Non-profound autism increased much more, which makes sense given the broadening of criteria. The study is https://pmc.ncbi.nlm.nih.gov/articles/PMC10576490/

Anecdotally, any speech therapist with a long career will likely remark on a local increase of severe autism cases over the last 20-30 yrs. It's not as "skyrocketing" as ASD stats, but prevalence has likely increased substantially.

There are apps that help kids on the autistic spectrum to communicate, and flashcard systems, and we're experimenting with these, but they're more geared towards encouraging the child to communicate. In our case, he communicates fine with gestures, nudges, pointing at things he wants, bringing flash cards of foods he wants, eye contact etc. And he seems to have good cognitive skills in terms of puzzles, basic arithmetics and counting, memory, etc. It is learning language as an auditory system that seems to be really difficult.

Adam can 'read' in the sense of knowing and recognizing all the letters (he takes delight in that) and pronounce the few syllables he's able to when he sees them written out (mostly consonants m,n,h with vowels a,o,e). His phonematic understanding for other syllables exists but is poor (e.g. he has trouble choosing between a BAH card and a PAH card when I say one of them out loud, whereas the letters B/P in isolation are easy). My idea is to build an app/site which teaches him and reinforces three-way connections [picture]<-->[written form]<-->[sounds] by letting him "type", initially by pecking at large squares with letters on screen, rather than an entire keyboard. So for example, there's a picture of him at the top, a row of 4 big blank squares underneath the leftmost of which is blinking, and 7-8 letters strewn around at the bottom, from which he can type in sequence A-D-A-M and get a sound effect of victory. For words he doesn't know or remember, there's a mode where he just needs to repeat e.g. C-A-T which is already written in identical squares in a separate row just above, then after a few successes the hint row goes away. For an MVP in which I can quickly backfill 100-200 simple words like that, and track progress, this would already, I think, be valuable; then maybe I can add a mode where the words sounds (with or without the picture) and he needs to type it.

If all this works for simple words, and he takes pleasure in typing, the stretch goal is to turn from words into short sentences, and both teach him phrases like I WANT [X], or WHERE IS MOM?, and let him request stuff with such phrases. None of this directly addresses the apraxia problem of actually learning to move his lips/tongue/throat/etc. appropriately, but I hope it can create more scaffolding around our efforts in that area (which we try very hard to work on daily) and together help him build an understanding of language/syntax. I'm very worried that, despite ongoing (very slow) progress in both speaking and understanding, phrases, sentences, syntax seem to elude Adam's grasp, and time is running so very fast.

I've been a backend/systems developer almost all my life, with not a lot of frontend experience (although I do know basic HTML/CSS/JS), and no app development. So I'm thinking for now to prototype this as a web page/pages, maybe using a lightweight framework rather than vanilla HTML (not sure), and let him interact with it on the iPad. I'll try to get the basic visual elements (picture/rows of squares for typed letters/bag of letters to choose from below) right with CSS/JS, and see if I can iterate from that. That's the idea, currently.

(Well, the only kind on offer, really.)

Comments URL: https://news.ycombinator.com/item?id=39876590

Points: 83

# Comments: 128

Comments URL: https://news.ycombinator.com/item?id=39077699

Points: 3

# Comments: 0

2. When you proofread and fix typos, do you contribute the fixes back upstream?

Comments URL: https://news.ycombinator.com/item?id=31665302

Points: 2

# Comments: 0

One thing the OP didn't mention that I really liked was runtime checks on array/slice access and integer under/overflow. Because dealing with heap allocation is a bit of a hassle, I was incentivized to use static buffers a lot. I quickly figured out that I didn't have to worry about their sizes much, because if they're overrun by the unexpectedly large input or other behavior in my algorithms, I get a nice runtime error with the right line indicated, rather than corrupt memory or a crash. Same thing about choosing which integer type to use: it's not a problem if I made the wrong choice, I'll get a nice error message and fix easily. This made for a lot of peace of mind during coding. Obviously in a real production system I'd be more careful and use dynamic sizes appropriately, but for one-off programs like these it was excellent.

Overall, I really enjoyed using Zig while starting out at AoC problem 1 with zero knowledge of the language. To my mind, it's "C with as much convenience as could be wrung out of it w/o betraying the low-level core behavior". That is, no code execution hidden behind constructors or overloads, no garbage collection, straight imperative code, but with so much done right (type system, generics, errors, optionals, slices) that it feels much more pleasant and uncomparably safer than C.

(you can still get a segmentation fault, and I did a few times - by erroneously holding on to pointers inside a container while it resized. Still, uncomparably safer)