Hacker News Reader

Comment by EGreg | Hacker News Reader

anyone actually use comma-first syntax? It lets you easily move lines around, too:

  {"foo": "bar"
  ,"baz": "hehe"
  ,"yes": "aligned"
  ,"better": "this way"}

View on HN

Haskell culture tends to do this kind of stuff for records, FWIW. Of course, in this case, it might even make sense to render this in a way such as the following:

  {
    "foo": "bar"
  , "baz": "hehe"
  , "yes": "aligned"
  , "better": "this way"
  }

Because as another person already said, the first line isn't movable, and the last line wasn't either. The first key-value pair does look a tad strange because it doesn't have anything before the key, but nevertheless, now changing things is even easier.

Admittedly, it would look nicer if we could have trailing commas, though. Oh well, we have YAML for extra readable record syntax, even with how horrible YAML can get in reality.

My opinion: just have commas be optional, like semicolons.

Allow linebreaks to insert implied commas

This has the same number of lines that can’t be moved freely as comma at the end.

But visually easier to check Also you can put the last brace on its own line

> But visually easier to check

I’ll agree with that, since they’re all vertically aligned.

> Also you can put the last brace on its own line

You can always put the first and last brace on their own line in most languages whether the commas are at the front or end.

But in the comma-first case that lets the last line be movable, that was my point basically.

Not the top one!

more easy how?

Reply on news.ycombinator.com