News for hackers. Stuff that matters.
Re:The Ruby Style Guide by steveklabnik on Friday June 14, 2019 @12:34PM (#20184312)
I made a comment on this thread[1] in 2014, and it was closed two days ago. I wondered why... guess this is why!

1: https://github.com/rubocop-hq/ruby-style-guide/issues/273

Re:The Ruby Style Guide by nixpulvis on Friday June 14, 2019 @01:30PM (#20184822)
This thread is interesting to me, since I've changed my mind on this topic since I originally commented. :P

I blame Rust, and macros.

Re:The Ruby Style Guide by hartator on Friday June 14, 2019 @01:10PM (#20184629)
I don’t fully get your point. There is no official style guideline for Ruby.
Re:The Ruby Style Guide by steveklabnik on Friday June 14, 2019 @01:32PM (#20184853)
I'm not sure what your point is either. Mine was "oh, there's a website now; they must have been reviewing old issues to prepare for the launch." There is no "official" style guide, you're 100% right, but I'm not sure what that has to do with this.
Re:The Ruby Style Guide by hartator on Friday June 14, 2019 @01:46PM (#20185001)
Oh, got you. I thought you were implying some conspiracy to kill conversation or something. Nvm.
Re:The Ruby Style Guide by steveklabnik on Friday June 14, 2019 @01:57PM (#20185087)
Ah, yeah, no worries! I was not :)
Re:The Ruby Style Guide by hartator on Friday June 14, 2019 @02:04PM (#20185167)
It's actually an interesting thread. My take would have been to use comma when it's something we intend to modify, no comma when it's not. So intent is explicit.

Like:

    STATES = [
      :success,
      :error
    ]

    SUPPORTED_LANGUAGES = [
      "en",
      "es",
      "fr",
    ]
Re:The Ruby Style Guide by bozhidar on Tuesday June 18, 2019 @12:36AM (#20209823)
Yeah, you're right. I was triaging and cleaning up the open issues prior to launching the new site.

Now that the guide has more editors I'm optimistic that we won't end up in a situation with that many non-triaged tickets down the road.