The DSM-5 introduced three ASD levels of severity: level 1 (“requiring support”), level 2 (“requiring substantial support”), and level 3 (“requiring very substantial support”).

https://www.autismspeaks.org/levels-of-autism has a good complete overview.

There's a cost attached to them, but it was decided that that cost is worth the significant benefits in road safety for both the people in the vehicle and the people around the vehicle.

You get no ecosystem benefits though, it's really just plain Android.

Brutal, and very accurate. This is great!

When you'd annotate a React component with ReactXHP (if I remember correctly), some codegen would generate an equivalent XHP components that takes the same props, and can just be used anywhere in XHP. It worked very well when I last used it!

Slightly less related but still somewhat, they have an extension to GraphQL as well that allows you to call/require React components from within GraphQL. If you look at a random GraphQL response there's a good chance you will see things like `"__dr": "GroupsCometHighlightStoryAlbumAttachmentStyle.react"`. I never looked into the mechanics of how these worked.

- The underlying firmware for the Marvell WiFi controller that Sony provided when they updated the PSP to support WPA (with AES) also supports WPA2 (with AES).

- Sony never set it up on the userspace side, perhaps for stability reasons or because there was no demand and they preferred playing it safe.

- The patches swap out the userspace bits to talk WPA AES with the ones for a WPA2 AES. The difference isn't huge, it's mostly changing data in some management frames and configuring the key exchange differently.

It's very impressive that that developer found the right things to patch, with the right values.

Looks like it has been in the works for a while.

https://psp-archive.github.io/apps/wpa2.html

https://arstechnica.com/uncategorized/2005/04/4865-2/