Yes, it's called "D-K Posterboy-itus".

Congenital, I think.

Meet Pop.

"works fine" -ish?

Aim for the stars, be happy with the moom, but don't be surprised if you get lost in space.

Okay, I added that last bit, but it seems so appropriate here.

One popular thing that works on Windows and not on Linux is Apple Mobile Device Service. This is the component of iTunes that lets a user sync MP3 albums, such as those bought on itch.io or Bandcamp, onto the Music app of an iPhone over a USB cable. As a driver, it is outside the scope of Wine.

Until the maintainer receives an issue report requesting a package for a particular distribution. For every one report, there are probably dozens of cases where another prospective user considered using a particular piece of software but did not because there was no package.

I read Package Forge's inclusion criteria. In order to get distributed in PkgCache, the application first needs to "be a well known package" and listed on a website called Repology. And Repology's inclusion criteria appear to be meant for distributions' repositories, not individual project maintainers' repositories.

Provided your application already has enough users compiling it from source code to justify packaging it in the first place.

I think allo is referring to the "game-key cards": Nintendo Switch 2 cartridges that contain the title screen and nothing else, where the whole game is shipped as a day-one update. At least on the original Switch, Nintendo required the first few missions of the single-player campaign to be on the cartridge. Among early physical games for Nintendo Switch 2, only Nintendo's first-party games and CD Projekt's Cyberpunk 2077 weren't game-key cards.

It'd look like a subset of C where the compiler emits a diagnostic for every undefined behavior that's practical to detect at compile time and inserts code to catch at runtime everything else the standard calls undefined. The first step toward this is what GCC already does for -Wall -Wextra -pedantic -fsanitize=address,undefined. The second step is that a pointer variable doesn't contain a raw address but instead a base address and index, and every dereference of an array member is bounds-checked against the size of the object it came from. This ends up making the language's strict aliasing rule even stricter, and a lot of pointer casts or union puns become undefined and therefore errors. After programmers become accustomed to stricter pointer provenance, a compiler maker can add a concept of ownership, with a borrow checker to detect use-after-free and the like.

If the only programs with permission to escape the language's type system are system libraries signed by the operating system publisher, it isn't "totally useless." It'd be like Java applets, J2ME phone applications, Silverlight applets, XNA games, and Windows Phone 7 applications. Executables for these platforms are in an intermediate representation that lets the loader tell if unsafe was used. If the executable contains unsafe code but isn't signed with the permission to escape the sandbox, the loader raises a security exception. Applications were expected to perform I/O through first-party system libraries signed with this permission. Third parties weren't supposed to be doing "systems programming" on these platforms.

"Addressing" can mean "acknowledging" as in "Frock acknowledged the privacy concerns of its technology, then proceeded to lie about its ubiquitous survellance data...."

Or, to put it another way: "Dear person with privacy concerns, let me address them by simply saying 'Frock you!' Sincerely, Frock executive."

I don't know about you, but when I'm driving and I see a police car, if there's little or no other traffic I make sure I'm at or below the speed limit. If I'm in moderate traffic going the speed limit, I wait until the cop is out of sight for a minute or two before trying to pass. If I'm in heavy traffic I'm probably stuck in a pack, so it doesn't matter.

In the first two scenarios, my increased attention to my speed probably has a non-zero improvement in safety for the moment in question.

Back to your original point:

I don't have any citation to back this up, but I've heard that for most crimes, the certainty of being caught is a stronger deterrent than the expected punishment. Unfortunately, "near certainty of being caught" when you break the law is pretty much the definition of a police state. As long as "X" is tolerably low, I would rather live in a country where I have X% chance of being a victim of a particular type of crime in a given year with less survellance than where I have 0.5X% chance with more survellance.

Is even shooging against the law now?

"Convincing would-be criminals they will be caught" does nothing to deter the person bent on suicide (like the Brown University murderer) or the person who intends to be caught (people engaged in civil disobedience expecting to be arrested to make a point).

There's not much that can stop someone who is 1) smart enough to pull off a crime, and 2) determined to commit the crime no matter what the consequences.

Deterrence keeps honest people honest and it sometimes keeps those who are dishonest but who do don't want to face the consequences honest - or at least it makes them think about committing a different crime or committing the crime in a different place, one where he's either going to face tolerable consequences if caught or where he believes his chances of being caught are tolerably low.

He was dead for 2 days when they found him. He had things with him that tied him to Brown University murders and I think to the MIT professor's murder. He would've been found eventually without any assistance from Flock or from the eyewitness.

The only thing that the eyewitness and Flock provided was a quicker end to the manhunt. Given that people in the Brown community were living in fear that a gunman was still out there, this is still worth something. Is it worth living in what is a few short steps away from (or arguably, already) a police state? That's a question society will need to answer.