Very different niche from the StarFighter but StarLabs make excellent machines.

    #!/usr/bin/sh

    while true; do
        reset;
        "$@";
        inotifywait -e MODIFY --recursive .
    done

    clobber(
      document.body,
      h("marquee", [
        h("span", {"style": "font-weight: bold"}, "Hello"), ", ",
        h("blink", "world"), "!",
      ]),
    );

Prompted by the post on millionjs, which compiles user code to hit the same outrageously small size target.

Comments URL: https://news.ycombinator.com/item?id=32293880

Points: 23

# Comments: 4

It's starting to get a bit of momentum. We have users across a few different companies and some consistent contributors (thank you, in particular, jgberry). We're reaching a point of stability, and would like to gather some final feedback before hitting the big 1.0.

Comments URL: https://news.ycombinator.com/item?id=31395133

Points: 2

# Comments: 0

With backwards sorting you know that, unless there is a cycle, you can always scroll up from a call site to find the definition or down from a definition to see where it is used. With forwards sorting you can scroll down to find a definition, unless the function was imported, or used as a decorator somewhere, or called by something that was used as a decorator, or used in some other way that I haven't thought of.

My personal experience is that this predictability is hugely useful. It almost entirely obviates the need for jump-to-definition within a module, and gives modules a very obvious shape and structure.

SSort is currently used for several hundred kilobytes of python so I'm wary, but if I'm going to make a breaking change before 1.0 then I think this is likely to be it.

0: https://github.com/bwhmather/ssort

1) To provide a code-level record of what has changed in individual files and why.

2) To provide a high-level record of what features were introduced and what bugs were fixed over a period of time.

Often people will forget about one of them when arguing for a particular approach.

Squashing can make 2 easier but annihilates 1. Rebasing gives you 1 but makes 2 difficult, or requires that you track high level changes in an external system. In theory, approaches using merge commits can give you both but they are often difficult to apply in practice.

See the notes in sd_notify(3) or https://lists.debian.org/debian-ctte/2013/12/msg00230.html for a simple alternative implementation. Admittedly could be better documented.

edit: point to notes section