News for hackers. Stuff that matters.
Re:Making Netflix.com Faster by tylermauthe on Wednesday August 05, 2015 @09:30PM (#10014082)
Beautiful use of modern JS development techniques: client-side rendering, isomorphic JavaScript and smaller more-efficient libraries.

Even better to see these techniques applied appropriately, instead of slathered on to the point of being detrimental.

Also, +1 for using jQuery and being proud of it! :)

Re:Making Netflix.com Faster by code_sterling on Wednesday August 05, 2015 @10:01PM (#10014158)
> Also, +1 for using jQuery and being proud of it! :)

That wasn't the takeaway some of us read here, and honestly, that's just foolish. Take pride in your craftsmanship, never take pride in your tools. I love my hammer, but when I need a screwdriver, it's a stupid choice.

Re:Making Netflix.com Faster by ProCynic on Wednesday August 05, 2015 @10:41PM (#10014258)
On the other hand, don't be ashamed of using a tool that works for the job, even if it isn't the latest or coolest thing. jQuery is no longer the best choice for a lot or circumstances, but if it is for yours, go for it.
Re:Making Netflix.com Faster by dikaiosune on Wednesday August 05, 2015 @09:47PM (#10014130)
It reads like jQuery was part of the server-rendered Java stack, and there's no mention of it in their Node/React stack.

I use jQuery and am proud of it, but it looks like that may no longer be the case at Netflix?