My frontend builds fail because of trailing commas in the code (by design, so technically a non-issue). At the same time, my editors can balance parens but they can't really do anything but complain about trailing commas. It can't assume it's an issue and "fix" it because I just might not be done writing, yet. My editor can make more and safer assumptions about paren balancing, however, and so it does.
I really have no horse in this race, neither of these things bother me. I just can't help but notice that the paren problem in particular can be easily rectified.
Re:The rise and rise of JSON (2017)
by TuringTest on Monday August 27, 2018 @11:11AM
(#17851951)
Yeah, I concur. I mean, instances have a "global stream" where all posts from all users are sent? What's the use for that?
It would be like Facebook or Twitter having a "front page" showing all posts from all their users. I don't want to read what something posted merely because they're subscribed to the same physical server. There should be some classification of affinity by common interests.
That said, I cede that they are different. I just don't get the hate of parens.