Readit Newshttps://kotaku.com/unity-ironsource-merger-ad-tech-layoffs-1...https://mobilegamer.biz/inside-unitys-troubled-4-4bn-ironsou...https://unity.com/news/unity-completes-merger-ironsource
He does not have access to any form of social media.
His friend list is limited to people he knows irl.
Activity on all devices is monitored (Google family link) and controlled (pi-hole, DNS blocking, ad blocking etc).
The internet is a cesspool and I agree we should limit children from free access to this - but telling kids to stick to pen and paper until they are 13 isn't the way to do it.
If the asteroid were to strike, let's say somewhere on one of the continents, the resulting destruction would be similar to the simultaneous detonation of at least a few thousand nuclear bombs minus the particle radiation..... but with so much more impact energy.
This would generate a near-instant super-heated, molten crater at least 15km across and immediately followed by a hypersonic blast wave that would utterly annihilate everything within a radius of at least a couple hundred kilometers. The even faster-traveling thermal pulse in between those two would flash-fry any flammable thing out to maybe twice the distance of the blast wave, and even at the outer edge of said thermal pulse, this includes causing lethal, almost total third to fourth-degree burns over any living tissue.
It would not be a good day for the people of whatever wider region that surrounds its impact point.
Globally, we'd also see atmospheric effects. They'd be nothing like the ones that struck the dinosaurs down into near total extinction, but they'd be noticeable, and would cause social, economic and environmental havoc. It would maybe be comparable to something like the 1815 Tambora eruption, whose climatic effects basically killed summer for much of the world in that year. Only here it would happen in modern times and from a much scarier type of disaster, hammering delicate modern infrastructure and communications.
If Apophis struck somewhere fairly densely populated, like, say, the Eastern U.S, almost anywhere in Europe or somewhere in central to Eastern China, in just seconds we'd have close to the biggest human death toll from a natural disaster in all our history, and the second-order effects of it would kill millions to tens of millions more. I can only think of the Black Death or maybe the 1918 flu pandemic as candidates for worse, albeit much slower killing.
If Apophis were to hit the ocean, things get a bit harder to estimate and guesstimate.
On the one hand, it's "only" 450 meters across, and much of the ocean is damn deep, enough so as to swallow the asteroid whole and mitigate much of its more fiery atmospheric effects. On the other hand all that kinetic energy still has to go somewhere, and so in this case, perhaps creates a massive ocean-spanning series of tsunamis that hit thousands of kilometers of coastline with waves big enough to drown tens of millions of people.
Then again, maybe the word drown doesn't quite describe it. More accurately these waves would be pulverizing, smashing the victims in their way into surrounding objects with enough force to cause catastrophic tissue and bone trauma. Millions would be smashed to death much much faster than they could drown. In a way, it would be something of a mercy.
Fun stuff.
I think you answered this with the rest of your comment.
More recently, I’ve been teaching a 3 year old letter sounds and he loves running around finding signs saying “Dad” I found a “duh”. “Duh duh duh!” (For D). Kids really just want to hang out with you so, it’s ok to just throw in some letter sounds or number counting ideas in here and there. You’ll be surprised what they pick up!
I find the complexity to still feel awkward enough that makes me wonder if deleted_at is worth it. Maybe there are better patterns out there to make this cleaner like triggers to prevent deletion, something else?
As for the article, I couldn't agree more on having timestamps / user ids on all actions. I'd even suggest updated_by to add to the list.
> oneof fields can’t be repeated.
Wrap oneof field in message which can be repeated
> map fields cannot be repeated.
Wrap in message which can contain repeated fields
> map values cannot be other maps.
Wrap map in message which can be a value
Perhaps this is slightly inconvenient/un-ergonomic, but the author is positioning these things as "protos fundamentally can't do this".