porkbrain

Unfortunately, some apps don't support text selection and on some websites the text selection is unpredictable.

I'd actually compare screen OCR to screenshots. Instead of every app and every website implementing their own screenshot functionality, the system provides one for you.

Same goes for text selection. Instead of every context having to agree on tagging the text and directions, your phone has a quick way of letting you scan the screen for text.

To be fair, I still use the "hold the text to select it" approach when I want to continue with the "select all" action and have some confidence that is going to do what I want.

Fair point, it does not on my device

Text selection used to be frustrating on mobile for me too until Google fixed it with OCR. I get to just hold a button briefly and then can immediately select an area of the screen to scan text from, with a consistent UX. Like a screenshot but for text.

Used for example to write GTA SAMP modes. I remember writing them in Pawno IDE. The scripts would get large as I'd export positions of many objects and paste them into the scripts to spawn in game. Makes for an okey "how I started programming" story.

Exactly. In my region there are multiple tournaments a month (in season) where players from no ELO to 2300 play. Swiss system means you're going to be paired up/down.

I'm ~1900 which means first two rounds are typically beginners.

I've promoted to rook several times in over-the-board tournaments.

It's easier and quieter than stopping the clock and searching for a free queen piece if your position is decisive and your opponent stubborn. Or your piece to be captured immediately. So not necessarily "cocky" as the answers suggest but rather "mindful to other players".

I imagine they would counterargument your proposal along the lines of: "the most endangered children cannot rely on their families to protect them online"

No, according to Wikipedia Planet Nine is expected to have about 5 earth masses.

You can cascade the deletes in db layer rather than in app layer

1. Have a global append-only function key-value store.

2. A key of a function is something like `keccak256(function's signature + docstring)`

3. A value is a list of the function's implementation (index being the implementation's version) and some other useful metadata such as the contributor's signature and preferred function name. (Compiler emits a warning that needs to be explicitly silenced if preferred name is not used.)

4. IDE hints and the developer confirms to auto import the function from the global KV store.

5. Import hash can be prepended with a signers name that's defined in some config file. This makes it obvious in git diffs if a function changes its author. Additionally, the compiler only accepts a short hash in import statements if used with a signer.

package.toml

  [signers]
  mojmir = "mojmir's pubkey"
  radislava = "radislava's pubkey"

source.file

  // use publisher and short hash
  import "mojmir@51973ec9d4c1929b@1" as log_v1;
  // or full hash
  import "51973ec9d4c1929bdd5b149c064d46aee47e92a7e2bb5f7a20c7b9cfb0d13b39" as log_latest;
  import "radislava@c81915ad12f36c33" as ln;

  log_v1("Hello");
  log_latest(ln(0));