JoeyJoeJoeJr

Short clips is a common technique for spotting AI generated videos. It's computationally expensive to do more than that. Not impossible, but uncommon.

https://youtu.be/M4TXO4kQwSQ?t=2m17s

They updated the ride after the movies, so... It's kind of circular at this point.

Hot take:

Ive is a terrible designer who consistently let his idea of good aesthetics take priority over usability, durability, and repairability.

He's dead on about these products, but it's big talk from the guy responsible for the trash can Mac, magic mouse 2, butterfly keyboard, hockey puck mouse, etc.

Usernames are a thing now, so it's no longer necessary to share your phone number with other users.

Raster images do not need to be rendered - see Rendering:

Rendering is the process of generating a photorealistic or non-photorealistic image from input data such as 3D models...Today, to "render" commonly means to generate an image or video from a precise description (often created by an artist) using a computer program.

Note that "render" is a fairly generic term, and it is sometimes used like "render to the screen," to just mean to display something. Rasterisation may be a better term to use here, since it only applies to vector graphics, and is the part of the process I am referring to.

In any case, except for possibly reading fewer bytes from disk, the vector case includes all the same compute and memory cost as the raster image - it just has added overhead to compute the bitmap. On modern hardware, this doesn't take terribly long, but it does mean we're using more compute just to launch/load things.

It's also worth noting apps have to ship higher resolution assets now, due to higher resolution displays. This can include video, audio, images, etc. Videos and images may be included at multiple resolutions, to account for different sized displays.

For images, many might assume vectors are the answer, but vectors have to be rendered at runtime, which increases startup time in the best case scenario, and isn't even always supported on all platforms, meaning they have to be shipped alongside raster assets of a few different sizes, further increasing package bloat. And of course the code grows to add the logic to properly handle all the different asset types and sizes.

All this (packaging dependencies, plus assets/asset handling) to say it isn't always malware, ads, electron, etc. Sometimes it's just trying to make something that looks nice and runs well (enough) on any machine.

Many apps ship both vectors and raster images. It is worth nothing that vectors save space, but increase compute (the image now has to be rendered at runtime), contributing to slower startup times.

Worth noting is that "good" database design evolved over time (https://en.wikipedia.org/wiki/Database_normalization). If anything was setup pre-1970s, they wouldn't have even had the conception of the normal forms used to cut down on data duplication. And even after they were defined, it would have been quite a while before the concepts trickled down from acedmemia to the engineers actually setting up the databases in production.

On top of that, name to SSN is a many-to-many relationship - a single person can legally change their name, and may have to apply for a new SSN (e.g. in the case of identity theft). So even in a well normalized database, when you query the data in a "useful" form (e.g. results include name and SSN), it's probably going to appear as if there are multiple people using the same SSN, as well as multiple SSNs assigned to the same person.

I've had the same problem with HeliBoard learning garbage. I just changed my settings though, and I think it should help:

1. Open HeliBoard settings
2. Open Text correction settings
3. Scroll all the way to the bottom, and turn off "Add words to personal dictionary"

If you scroll all the way to the top again, you can manually manage the personal dictionary, including adding words you do want, and deleting any junk that was added by mistake, before switching that setting off.

I think to be fair, you've got to compare his before and after, rather than comparing him to anyone else.

I certainly wouldn't say he looks young, but I think he's on a better trajectory.

Someone testing on themselves is how we learned what causes and how to treat ulcers (the researcher earned a Nobel prize for giving himself an ulcer, and then treating it), among other things.

Controlled trials are great, but research has to start somewhere.

Flanders is self employed - he owns the Leftorium. There's a joke in this episode about not writing off the ink used to print receipts as a business expense, because he likes the way it smells. He can do his taxes when he wants.