I am aware of classifications and content descriptions. I’m not in US so the ESRB are not directly relevant but my local body does something similar.

I find the actual classifications to be a bit conservative so treat them all as advisory and make my own decisions. For example my son beat these (on easy) at four years old, I don’t think we would have enjoyed them as much if we waited until fifteen:

• https://www.classification.gov.au/titles/transformers-devastation
• https://www.classification.gov.au/titles/marvels-spider-man

On the other end of the scale I can use these descriptions to see that while Saints Row (2022) is tamer than GTA5 it is still going to have content thats a bit rough for an eight year old:

• https://www.classification.gov.au/titles/grand-theft-auto-v
• https://www.classification.gov.au/titles/saints-row-1

Parental controls are another question but I use then for time limits on his tablet and content restrictions on consoles and streaming services.

The way I have parental controls set up he has access to everything M or lower but MA15+ or higher requires a conversation.

They help inform my decisions but at the end of the day we are making our own choices within our household.

🎉

They put a lot of care into that announcement page and showing the major features visually. Great job!

Around 8 times a year.

I take my son to the barber and we have a haircut together.

If it was just myself I wouldn’t notice when my hair was long but I can see it on him so I know when its time.

Great to see!

I tend to just use the betas for a quick smoke test to check my project still builds.

The RCs are generally stable enough to use as a daily driver. And if for some reason its not then now’s the time to find those bugs before the release.

Nice!

Stupid article needs a before and after comparison.

Instead it has way too many ads.

“It’s a bit technical,” begins Birdwell, "but the simple version is that graphics cards at the time always stored RGB textures and even displayed everything as non linear intensities, meaning that an 8 bit RGB value of 128 encodes a pixel that’s about 22% as bright as a value of 255, but the graphics hardware was doing lighting calculations as though everything was linear.

“The net result was that lighting always looked off. If you were trying to shade something that was curved, the dimming due to the surface angle aiming away from the light source would get darker way too quickly. Just like the example above, something that was supposed to end up looking 50% as bright as full intensity ended up looking only 22% as bright on the display. It looked very unnatural, instead of a nice curve everything was shaded way too extreme, rounded shapes looked oddly exaggerated and there wasn’t any way to get things to work in the general case.”

This should have been easy enough to illustrate.

Edit: Here is a greyscale illustration of a similar phenomenon:
From https://www.odelama.com/photo/Developing-a-RAW-Photo-by-hand/

Of course in reality it get a bit more complex when we perceive colors as having different brightness too:

From https://www.vis4.net/blog/avoid-equidistant-hsv-colors/

You can play with the filters here:

https://steamdb.info/sales/?min_discount=80&min_rating=80&min_reviews=500

Most laptops have a physical slider that can mask the camera. But I don’t know of any tablets or phones that offer this feature.

This sounds like a jump the shark moment

As far as i can tell the loan was for around 4.5 months average salary for Brazil. Its a windfall but not a “retire early” windfall.