m93a

{
  "content_metadata": {
    "chapter_info": {
      "brandIntroDurationMs": 1532,
      "brandOutroDurationMs": 3204,
      "chapters": [
        {
          "length_ms": 15928,
          "start_offset_ms": 0,
          "start_offset_sec": 0,

m93a

{
  "content_metadata": {
    "chapter_info": {
      "brandIntroDurationMs": 3924,
      "brandOutroDurationMs": 4945,
      "chapters": [
        {
          "length_ms": 22959,
          "start_offset_ms": 0,
          "start_offset_sec": 0,

m93a

declare const Zero: unique symbol;
type Zero = { [Zero]: true };

declare const Succ: unique symbol;
type Succ<T> = { [Succ]: T };

type FirstElementOrZero<Arr extends any[]>
    = Arr extends []
    ? Zero
    : Arr[0];

m93a

Prompt

If one were to create a custom OS for a DIY microcontroller-based device (for example a cyberdeck or a feature phone), what unorthodox design decisions could they take to make to make the OS interesting from a computer-theoretical standpoint? Two examples that come to my mind are: designing the OS to be used on a heterogeneous set of cores, each having different performance and capabilities; and making all executables sandboxed via WebAssembly, with configurable privileges.

Response

Creating a custom OS for a DIY microcontroller-based device with unique and theoretically interesting design decisions can lead to fascinating and innovative results. Here are several unorthodox ideas you might consider:

1. Heterogeneous Core Utilization

As you mentioned, using a heterogeneous set of cores with different performance and capabilities can lead to interesting challenges and solutions:

• Dynamic Task Allocation: Develop algorithms for dynamically allocating tasks to the most appropriate core ba

m93a

[
    {
    "key": "ctrl+alt+o",
    "command": "runCommands",
    "args": {
      "commands": [
        "outline.removeView",
        "workbench.action.focusActiveEditorGroup"
      ]
    },

m93a

#!/usr/bin/env nu
const p = ~/.bin/flatpak
rm -rf $p
mkdir $p
(
  flatpak list --columns=application
  | lines
  | where (str contains "Platform" | not $in)
  | where (str contains "Gtk3theme" | not $in)
  | each {|v| [$"($p)/($v)", $"#!/usr/bin/sh\nflatpak run ($v)"]}

m93a

Articles

• https://daily-dev-tips.com/posts/what-exactly-is-frontmatter/
• https://dpericich.medium.com/what-is-front-matter-and-how-is-it-used-to-create-dynamic-webpages-9d8dc053b457

Specs

• https://jekyllrb.com/docs/front-matter/
• https://pandoc.org/MANUAL.html#extension-yaml_metadata_block
• https://gohugo.io/content-management/front-matter/
• https://mystmd.org/guide/frontmatter

m93a

function x
  nohup fish -c "$argv &" > /dev/null && exit
end

function x_complete
  set arg (commandline -ct)
  complete -C$arg
end
complete --command x --arguments '(x_complete)'

m93a

Clamped Value

Idealized syntax:

component ClampedValue {
  in min: number;
  in max: number;
  
  out value = clamp(min, prev value ?? 0, max);
}

m93a

# taken from github.com/dandavison/nushell-config

export def 'set difference' [s2: list] {
  # nushell doesn't have a hash table so quadratic time complexity
  let s1 = ($in | sort | uniq)
  let s2 = ($s2 | sort | uniq)
  $s1 | where {|x| not ($x in $s2)}
}

export def 'set intersection' [s2: list] {