Netflix: Removing client-side React.js improved performance by 50%

Re:Netflix: Removing client-side React.js improved performan... by akerro on Friday October 27, 2017 @09:14AM (#15567939)

I just use lynx to browse and block downloading js files by default. I wrote this comment using ed and curl.

[ Parent | on HN ]

Re:Netflix: Removing client-side React.js improved performan... by nindalf on Friday October 27, 2017 @10:09AM (#15568403)

I don't know why you'd use such heavy duty applications for such a simple use case. I merely use a butterfly to induce cosmic rays to flip the bits of memory needed to send a http request.

[ Parent | on HN ]

Re:Netflix: Removing client-side React.js improved performan... by positivecomment on Friday October 27, 2017 @10:21AM (#15568548)

A butterfly is way more complex than React.js.

[ Parent | on HN ]

Re:Netflix: Removing client-side React.js improved performan... by tomxor on Friday October 27, 2017 @11:00AM (#15569011)

How true, in fact butterflies are more complex than all software put together :P you just broke that whole branch of xkcd jokes dammit!

[ Parent | on HN ]

Re:Netflix: Removing client-side React.js improved performan... by jnbiche on Friday October 27, 2017 @11:55AM (#15569602)

Ha, you kids and your fancy lynx browsers. I do just fine with Netcat and typing in the HTTP requests by hand. Works just fine!

[ Parent | on HN ]

Re:Netflix: Removing client-side React.js improved performan... by ry_ry on Friday October 27, 2017 @12:17PM (#15569802)

I wrote this with a torch and a length of fibre optic cable.

[ Parent | on HN ]