News for hackers. Stuff that matters.
Re:Best Practices Exist For A Reason by btilly on Wednesday May 02, 2012 @05:36PM (#3921339)
Indeed the link I gave demonstrates how the right IDE also solves this problem. The fact that there are many ways of solving the problem does not mean that it isn't a real problem that formatting can help address.
Re:Best Practices Exist For A Reason by ynniv on Wednesday May 02, 2012 @05:54PM (#3921403)
It is a real problem. Formatting can address it. That doesn't mean that formatting is the best solution.
Re:Best Practices Exist For A Reason by taligent on Wednesday May 02, 2012 @05:58PM (#3921420)
It means that there are ways of solving the problem that don't involve rewriting the code in a way that initially will confuse 99.999% of other developers.

And it is important in our industry to write MAINTAINABLE code.

Re:Best Practices Exist For A Reason by mattbriggs on Friday May 04, 2012 @12:27AM (#3927014)
if comma first confuses a dev more then half a second or so, they really aren't that good. First time I saw comma first was from a DBA about 10 years ago who swore by it, and it has been my go to technique for writing maintainable code in languages where you end up with huge comma separated lists.

I freely remove, add, and move things to the bottom of my js classes without ever hitting trailing semis, or hitting a missing semi. I think that is more maintainable then the alternative