How Firefox is Making JavaScript Debugging More Productive - Lately in JavaScript podcast episode 68

Summary Transcript

The first topic that we are going to talk about is making JavaScript pure. The idea is to write your code in a way that is more testable like passing parameters to functions than rather than passing values as global variables or variables defined outside the scope of the functions so they become testable.

The next topic is an interesting feature, actually I think this is very cool and it is implemented now in Firefox and I am sure other browsers will follow up because it's a well thought feature, very simple, which is to show you the pages that explain the errors that you may find in your error console, so if you have an error in JavaScript, now you have a link to a page, in this case to the site of Mozilla to explain that error. So this is very interesting and we will talk more about this.

Another article is about JavaScript variables hoisting, which this from what I understood, I was not familiar with this word, but is to gather all variable declarations in the beginning of the scope of the functions.

The next topic is about Web Sockets and server sent events, so this is more a tutorial to explain how you can implement applications based on Web Sockets with Node.js on the server side and JavaScript code on the browser side.

Then we talk briefly about the release of jQuery 3.0.

Then we talk about an article that defends test driven design, so called TDD, done on JavaScript. It tells about one weird trick that will change you code forever. I am not sure about that but we will there once it is its turn.

The next topic is about the spread operator which allows basically that a certain function takes a variable number of arguments and it is called how three dots changed JavaScript.

The next topic is just to briefly mention that EcmaScript 2016 language specification is finished, I suppose, I don't know if there will be revisions, but it's practically done.

Then there is an article that talks about 15 ways to write self documenting JavaScript, and it talks about good practices according to the author that seemed to well make the code more readable and self-explaining without comments. Personally I do not use much comments, so I already liked the proposal.

Finally there is one topic that talks about how WebAssembly can be implemented in practice in browsers that already support it.

Listen or download the podcast and RSS feed