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.

Mario Kart was played for racing, and balloon battles. Diddy Kong Racing was all about Fire Mountain (the game where you capture the eggs).

Yeah, moving the table was my first thought - felt very much in the spirit of the show. I also expected the hose to have holes, and/or be blocked in the middle. Having a functional hose in the far left bucket felt too easy.

You may have missed "also." The comment does not suggest replacing the current list.

Worth noting, the existing list dies actually appear to cover both known working and known not working apps - apps that do not work have their names given in strikethrough.

In college, in my intro to Java class, I had a program I'd written that I was trying to show someone. Every time I ran it (in Eclipse) it crashed. It had worked earlier, but was then consistently crashing. Looked at the stacktrace, looked at the code... No issues I could spot. After quite a while of poking around, with the file reverted to its original state and still failing, I did a select all, cut, paste (into the same file), and it started working again.

Some people have posted pictures in the thread now, and it looks like you might be correct. Seems odd - the blowhole is analogous to a nostril. Sucking something against your nose a swimming seems like it would be uncomfortable.

Under water, with no hands, how are they getting the fish in place? And perhaps more difficult, how do they keep it there? Anyone aware of a video?

Saw the movie today. I concur with this astute review.

I would say there were maybe (maybe) 4 spots where it made sense to put music, and maybe 1 or 2 of those where the scene and music were done well (graded on a favorable curve). Then about 20-25 places they jammed bad music for what felt like no reason other than to slow down a movie that already wasn't going anywhere.

I just saw it today. Can confirm - it's bad. Bad enough I'm upset it exists, because it practically taints the first.

The plot is pretty weak, and to make it worse, sporadically there are flashes that make you think it's finally building towards something, and then it just fizzles.

With very few exceptions, the songs are bad both in terms of the music and the lyrics, and they slow the movie to a crawl.

Additionally, Lady Gaga's lip synching is shameful, especially considering she's most famous for music. Her performance is otherwise fine, but it feels like they could have put anyone in there. She didn't bring anything to the role.

Joaquin Phoenix's performance is pretty good, and the cinematography is good. But... Don't see it. Definitely don't pay for it. I wish I had my money and my time back.

I've personally lived in places where the closest convenience store was 2.25 km, and the grocery store was nearly 18km, as well as places where a convenience store was literally a part of my building, and grocery stores were walkable distances.

The U.S. is enormous and varied. Take a look at truesizeof and compare the U.S. and Europe (don't forget to add Alaska and Hawaii - they won't be included in the contiguous states). Consider how different London is from rural Romania.

The president's "official act" would be issuing the pardon. The referenced Supreme Court decision just means it would not be a "crime" for the president to issue said pardon, not that the pardon would stand.

The president can't intervene at the state level. From americanbar.org:

A U.S. president has broad but not unlimited powers to pardon. For example, a president cannot pardon someone for a state crime.