I have a question regarding this formatting style:

    44100 AS sample_frequency
    , number AS tick
    , tick / sample_frequency AS time

I see this used a lot in Haskell, nix, and sometimes other languages (first time here with SQL)

. I personally find it very odd to read

. It feels like starting a sentence with a dot, instead of ending it with one, which feels quite jarring

. What is the primary motivation for employing this style, especially in languages (like SQL) where this doesn't seem to be the norm? And especially for the languages (Haskell, nix) where this is the standard (?) coding style, wouldn't it be preferable to use a different token as the separator, one that doesn't look as odd at the beginning of a line?

Less diff noise when adding/removing lines in a commit.

If you put the comma at the end, and then you need to add a line, you either:

* Insert the new item "in the middle" of the list. This is often possible, but not always.

* Add the new item to the end of the list, in which case the the line that was at the end before will now need to be modified to add a line.

Lines that begin with the coma can be more easily moved around/resorted. With the comma at the end, if you put the "last" item in the middle, you also need to add a comma at its end (and remove the comma from the new item that is now the final one).

Personally, I like languages where you can simply leave a comma at the end of a list or enumeration without this being deemed a syntax error (for example, in Lua the table {1,2,3,} is equivalent to {1,2,3} )

Aesthetically: Keeps the names lined up nice.

Practically: Overkill to avoid "no final commas in JSON" moments.

Haven't logged into my hn account in ages. But I did to say this: Awesome.

Confirm click artifacts in Firefox.

Wow. That's pretty insane. In a positive way :)

Absolutely insane concept! Bravo!