News for hackers. Stuff that matters.
Re:React+Flux can do in just 137 lines what jQuery can do in 10 by lhorie on Friday October 16, 2015 @10:10AM (#10399363)
Kinda linkbaity. As commenters in the article pointed out, the jQuery code omits the HTML and the React port has some functionality that is not present in the jQuery version, so the LOC comparison in the title is pretty meaningless.

The conclusion is that for a tiny one-off tool that can be banged out in 20 minutes, a big framework like React/Flux is completely overkill. But for large codebases where maintainability is a big issue, then React/Flux can be extremely useful (considering that's exactly the problem React/Flux try to address).

Am I the only one who thinks this stuff ought to be obvious?

Re:React+Flux can do in just 137 lines what jQuery can do in 10 by insin on Friday October 16, 2015 @11:54AM (#10400116)
This is more like what I'd expect a 20 minute React version to look like: http://bl.ocks.org/insin/raw/b2f4901d4173677908a8/
Re:React+Flux can do in just 137 lines what jQuery can do in 10 by insin on Saturday October 17, 2015 @01:20AM (#10403483)
And a Redux version because why the hell not: https://gist.github.com/insin/2f9a4cf810eeed88da89
Re:React+Flux can do in just 137 lines what jQuery can do in 10 by brackcurly on Friday October 16, 2015 @10:09AM (#10399357)
I think this blog post is pointless. Of course every abstraction adds some overhead at first. If your problem is simple enough to fit in a few lines of code you don't have to think a lot how you structure it.