MawKKe

In iOS, you can't even have more than one active timer at a time. Like wtf??? Also, when the timer or alarm clock triggers, you are presented with view containing two buttons (yellow and purple). One of them snoozes, one of them dismisses. Which one is which, you ask? You see, to keep things simple and consistent, the button actions (and labels) switch places depending on whether the view was triggered by an alarm or a timer. Oh! and the label text color is white, which makes it reeeeeeally difficult to tell which of the fucking buttons is which, especially in a rush or in the morning when your eyes are foggy.

I would have replaced this shitty ass app in a heartbeat, except Apples strict controls kneecap all third party apps by preventing them from running in the background...

Intel ca. 2010, probably

  <tree
    <leaf colour="green">
    <leaf colour="yellow">
  >

  <tree
    <leaf :colour green>
    <leaf :colour yellow>
  >

   (tree
     (leaf :colour green)
     (leaf :colour yellow))

  def foo(allowed: Optional[List[ElemType]] = None):
    allowed = allowed or []
    ...

I think 3b1b videos constantly break this rule; there is a LOT of going on visually, while the narrator is talking non-stop about some loosely related things or trivia. More often than not I have to re-watch segments multiple times because I cannot understand what the hell am I supposed to be paying attention to.

Wouldn't it make sense to have separate channels for distinct content streams (e.g game capture, face camera, overlays..) so that you could independently choose/optimize each channel's compression and thus make the whole stream more efficient?

I don't know anything about compression algorithms, but I hypothesize that maybe now the algos would also be able to do a better job since the frames have less abrupt discontinuities (in the viewport perspective).

This would also enable stream viewers's to activate/deactivate channels when needed. For example, when the overlay/webcam/etc occludes the view on layer (channel) below.

Why must applications incorporate implementation details of the deployment environment? Why does the environment owner not have tooling to control where files are placed?

Although sounds like your problem could also be caused by I/O saturation?

You can also select "black & white" mode for text documents which saves a ton of space

Also, you don't have to do manual stdout buffering. Have a look at ReadChapters function in here: https://github.com/MawKKe/audiobook-split-ffmpeg-go/blob/f95... (fyi it's my own repo)

(might be really buggy, let me know)