Peaking into the kind of JS problems that Netflix faces

While reading JS weekly, I ended up on a blog post from Netflix, about the kind of JS performance problems they face and how they resolved it. Pretty interesting to see the kind of problems some companies have. Improving the performance of our JavaScript inheritance model

Comments

Post a Comment

Popular posts from this blog

Chrome dev tools - secret weapon?

When I started working back in 2010, we used to support IE7. I still remember how much of a paint it was to debug javascript code. With IE8/IE9 debuggers, what I learned is patience, rather than figuring out how to fix all those weird bugs that *always show up *only in IE. The debuggers were so slow. Also back then, firebug was the norm. Chrome dev tools was relatively new and most people I knew did not use it. I liked Chrome so I sticked with it. Now, it's a tool that I use almost every day. In fact, I try to spend some time and follow what's new with the dev tools. I also spend some time experimenting with soon to be features/apis on Chrome Canary. This year, well last year... (2016), I've been pretty busy and haven't had much time to look at the new features. But today, I spent a few hours catching up on the last Google I/O and watch what's new with the dev tools. I wanted to share this link and give back some love to the chrome dev tools by writing this post.
Read more

converting videos with ffmpeg

I had to work on some video conversion and I found a good post from the Linux Journal on commands and tips for converting videos. http://www.linuxjournal.com/article/8517 A command example: ffmpeg -i eSeetrackFlash.flv -b 20000k -s 896x536 target_0.7.avi explanation to be continued
Read more