News for hackers. Stuff that matters.
Re:Jsfmt – Like Gofmt, but for JavaScript by sambeau on Friday May 09, 2014 @06:44PM (#7723644)
I think you might be missing the point here. gofmt doesn't only enforce a style guide, it has allowed the Go team to change Go's syntax and automatically update everyone's code.

This tool, to me, looks really useful for updating old javascript codebases - removing old library calls and polyfills — bringing in new native techniques.

Re:Jsfmt – Like Gofmt, but for JavaScript by secoif on Saturday May 10, 2014 @11:04AM (#7725630)
Nope, the point about adoption is spot on since you can already do this with esprima and other tools (e.g. substack's falafel/burrito or grasp) which already have a community. Outside of api flavour, they do the same thing. The differentiating factor is primarily which one will have stronger better community support.

My prediction is that since this is "go-flavoured", it will face some (unwarranted) adoption resistance amongst influential JS devs. This tool might attract new devs into the code manipulation space and they'll eventually converge on to the tool with strongest community support.

Re:Jsfmt – Like Gofmt, but for JavaScript by myg204 on Saturday May 10, 2014 @11:37AM (#7725758)
Well it's both really. The formatting fixes offered by gofmt are definitely a popular success. You always hear/read about how great it is to have completely removed the code formatting debates (and it is).
Re:Jsfmt – Like Gofmt, but for JavaScript by ihsw on Friday May 09, 2014 @07:45PM (#7723889)
> it has allowed the Go team to change Go's syntax and automatically update everyone's code

That's go fix.

Re:Jsfmt – Like Gofmt, but for JavaScript by dsymonds on Friday May 09, 2014 @08:11PM (#7723942)
Gofix does the work, but it is only feasible because gofmt exists.