A Prettier JavaScript Formatter

Re:A Prettier JavaScript Formatter by dangoor on Tuesday January 10, 2017 @12:35PM (#13366791)

I believe it was the "Nice attempt, but currently wrong." at the start of the comment. "Nice attempt" could imply that this should be thrown out in favor of another attempt to solve the problem.

[ Parent | on HN ]

Re:A Prettier JavaScript Formatter by n42 on Tuesday January 10, 2017 @01:46PM (#13367637)

The entire comment was patronizing. "Nice attempt" minimizes the effort involved and implies the author is a novice. "but currently wrong" categorizes the entire project as a failure because of a single bug. The followup "From my own experience writing a formatter" really drives the whole thing home.

[ Parent | on HN ]

Re:A Prettier JavaScript Formatter by artursapek on Tuesday January 10, 2017 @01:58PM (#13367775)

Classic HN :-)

[ Parent | on HN ]

Re:A Prettier JavaScript Formatter by tomp on Tuesday January 10, 2017 @03:12PM (#13368501)

Wasn't meant that way.

[ Parent | on HN ]

Re:A Prettier JavaScript Formatter by softawre on Tuesday January 10, 2017 @05:18PM (#13369713)

"Nice attempt" used to actually mean the words it said. You know, like "nice job".

[ Parent | on HN ]

Re:A Prettier JavaScript Formatter by acdha on Tuesday January 10, 2017 @12:48PM (#13366965)

Also, “currently wrong” is a really sweeping statement to make based on a single problem written in a fairly uncommon style. Yes, there are things which need to be fixed but that doesn't mean we have to be so dismissive of someone else's work which they've given away for free to the community.

[ Parent | on HN ]