Right, but on ISO keyboards have a vertical Enter key

Personally I like the ISO enter key way more than the ANSI one, it looks a lot more canonical for me and my pinky can press it better than the ANSI one.

My gender is ERROR_IN_NAME 😎

My goodness that makes my heart bleed.

To me it feels like this would work nicely for something that’s more tabular in nature, such as you mentioned, CSVs. But again, not all the time, which makes this formatting hard to use.

In some of my personal code I liked to have used it (in very specific circumstances, like having many similar-sized parameter declarations e.g. protobuf), but as you said the lack of support means that a lot of code formatters simply trim unnecessary spaces so they never stick around.

What’s more, I am still yet to find a consistent rule about when to apply this kind of formatting - the example in the article shows one for method args but it just doesn’t look good at all. Key-value lists (like maps) might be a good place to use it, but if one key ends up being very long you have a ton of unnecessary space, so I would need to “group” together similar-length keys to make it aesthetically pleasing:

const map = {
  foo:    1,
  bar:    2,
  bazbar: 3,

  // I don't want the keys above to be spaced to match this key
  someExtremelyLongKeyname: 4
}

When I saw the title I got confused with Node Package Manager lol

Thanks for the update @ernest, I noticed that there’s quite a few pull requests piling up on codeberg that requires your attention - will you be looking to merge these soon? Particularly the ones related to SQL injection seems like a high-priority: https://codeberg.org/Kbin/kbin-core/pulls

New Intel codename: Cornf lake