JavaScript Jabber

A weekly discussion by top-end JavaScript developers on the technology and skills needed to level up on your JavaScript journey.

Follow

122 JSJ Socket.IO with Guillermo Rauch

Guests :

Guillermo Rauch

Hosts :

Published : Aug 20, 2014

Duration : 48 Minutes

Show Notes

The panelists talk to Guillermo Rauch about Socket.io.

Special Guest: Guillermo Rauch.

Transcript

[This episode is sponsored by Frontend Masters. They have a terrific lineup of live courses you can attend either online or in person. They also have a terrific backlog of courses you can watch including JavaScript the Good Parts, Build Web Applications with Node.js, AngularJS In-Depth, and Advanced JavaScript. You can go check them out at FrontEndMasters.com.]

[This episode is sponsored by Codeship.io. Don’t you wish you could simply deploy your code every time your tests pass? Wouldn’t it be nice if it were tied into a nice continuous integration system? That’s Codeship. They run your code. If all your tests pass, they deploy your code automatically. For fuss-free continuous delivery, check them out at Codeship.io, continuous delivery made simple.]

[This episode is sponsored by WatchMeCode. Have you been looking for regular high-quality video screencasts on building JavaScript done by someone who really understands JavaScript? Derick Bailey’s videos cover many of the topics we talk about on JavaScript Jabber and are up on the latest tools and tricks you need to write great JavaScript. He also covers language fundamentals, so there’s plenty for everybody. Looking over the catalogue, I got really excited and I can’t wait to watch them all. Go check them out at JavaScriptJabber.com/WatchMeCode.]

[This episode is sponsored by Component One, makers of Wijmo. If you need stunning UI elements or awesome graphs and charts, then go to Wijmo.com and check them out.]

CHUCK:

Hey everybody and welcome to episode 122 of the JavaScript Jabber Show. This week on our panel, we have Jamison Dance.

JAMISON:

Hello, friends.

CHUCK:

I’m Charles Max Wood from DevChat.TV. And this week we have a special guest, and that’s Guillermo Rauch.

GUILLERMO:

Hey, everyone.

CHUCK:

Do you want to introduce yourself for the folks who don’t know who you are?

GUILLERMO:

Awesome, yeah. So, my name is Guillermo Rauch. And I was the co-founder and CTO of a startup called Cloudup that specialized in real-time volunteering. I’ve been using Node.js for a long time, created Socket.IO, which is a real-time framework for basically emitting events back and forth between clients and servers. And before that, I’ve always been involved in open source. So, I was part of the core team of developers of a framework called MooTools, and before that involved with different server-side PHP projects like Symfony, and always been in the open source ecosystem. Nowadays, I’m working at Automattic, which is a parent company of WordPress.com that acquired my company late last year, and still working on a lot of open source, which is part of our ethos and working really cool, real-time technology,

CHUCK:

Awesome. I didn’t know you were a Cloudup guy. I actually use Cloud.

GUILLERMO:

Awesome. [Chuckles] Yeah, for Cloudup one of the priorities was to basically make file-sharing as fast as possible. And that meant looking at every part of the stack from, how can we quickly show the upload before it’s done uploading? For example, how can we reproduce a thumbnail with HTML5? Or how can we transcode the video so that it’s easier to play on all devices. And a lot of different things that we took a look at optimizing, and HTML5 and JavaScript were a huge part of that experience.

And as far as real-time communication and Socket.IO are involved, one of the main priorities was to… when you share something we give you a link. And when you send someone that link, they start getting events about how that file or set of files changes over time. So for example, if I send you the file before it’s not uploaded, you get progress events. So, it almost feels like a peer-to-peer transfer. Or if the backend is doing a long-running job on your files, then the backends send you updates about how your file’s changing. Or if new thumbnails or conversions are ready, you get notifications. So, it was a great experiment in basically applying all these innovations to an old problem, which is transferring files.

CHUCK:

Very cool. So, we’ve got you here to talk about Socket.IO. And you mentioned one of the things that you do with the sockets. Do you want to just back up a little bit and explain what sockets are and why people should care?

GUILLERMO:

Yeah, definitely. So, I’ll actually back up and tell you how I got involved with JavaScript, which was I was developing a lot of server-side web applications that rendered HTML on the server. And I think a lot of people still are. Whenever we wanted to make a certain task faster, then Ajax came up. And we said, okay why would we go to the server and then fetch the entire HTML of an entire new page which involves a lot of moving parts? So, the server has to produce and handle the response, and it needs to call to the database for things that might not be related to a certain user action.

So, with Gmail, and I remember the web version of Outlook, we got access to this new APIs who were making asynchronous requests. And I think that took us really far in terms of making the web work for applications and not just websites, specifically as it relates to performance and responsiveness, right? We started seeing a lot of spinners everywhere, because we were performing some task that was asynchronous in nature and it was affecting only a portion of the page. So, we went from doing everything on the server and rendering all the HTML to making some parts of the application dynamic through Ajax.

But then, people as they recognized the value of the web as a platform for application and not just sites, wanted to start doing a lot of the things that they were doing on the desktop before, specifically chat applications for example, or applications where there’s a lot of data flow from the server to the client and from the client to the server. And what we found over time is that Ajax is lacking for making a lot of those kinds of applications, specifically what we call real-time applications. In many cases, it’s the server that wants to tell us something about the data and how it’s changing.

So, if you approach the problem for example of simply creating a chat application with Ajax, you find a lot of limitations. You start having to fight the model a lot, because you start for example polling. And then you say, “Well, I’m going to try to get updates every five seconds or so,” and then basically in the worst case scenario your chat messages arrive of course four or five seconds late. And just, the model doesn’t either because usually what you want to do is send messages in order, right? So, when you fire up asynchronous Ajax requests, they’re all going to go in parallel. And they’re going to and basically in a non-deterministic way, too, because the way that the TCP sockets work on a page is opaque to the developer. For example, it’s called XML HTTP request and not XML or HTTP socket. So, you’re operating at a higher level of abstraction.

So, I think a lot of the people that were working on these problems like Google or Facebook or Microsoft recognized that we needed a socket API. And the socket API just gives you a lot more liberty to create new protocols and new ways of passing data back and forth that we didn’t have before with Ajax. So, with WebSocket, we basically got a really clean API for bidirectional messaging. So, the server can send us something or we can send something to the server.

And when I was working with JavaScript a lot on the frontend, I thought, “Well, we can maybe bring this to the backend.” And Valerio, who was the core main developer of MooTools, came up with the idea of making MooTools compatible with the server-side. So, we started looking at things like Rhino, which was a Java-based JavaScript runtime that would allow us to run the same code on frontend and backend. And that’s how I start getting involved with server-side JavaScript.

And then another project that was closely related to MooTools came up which was called APE, Ajax Push Engine. And you see where things are going there, because that was, I think, in 2008 or 2009. Their idea was, “Okay. Ajax is fine, but we also need to push data from the server.” And that was actually an amazing project, because I think had it used the APE instead of the SpiderMonkey which was Mozilla’s JavaScript engine, I think it would have gotten to the place where Node.js is today, because they were extremely similar in their design. For example Node.js utilizes the kernel event API to basically handle all the connections in the same process in a very fast way. So, unlike traditional web servers like Apache 1, the way that it handles requests is a lot faster and it consumes a lot less memory.

So, that was the big difference at the time between Node.js and traditional web servers. But APE was actually doing that with their own wrapper around this kernel event APIs and it was plugging into SpiderMonkey. And that’s when I really, really got interested in running JavaScript on the server side because it would allow us to do this push of data very easily. And when Node.js came out, I basically wrote a WebSocket server. But then I realized WebSocket is just not enough for the kinds of applications that we need to build. It’s too simplistic.

So, that evolved into what’s Socket.IO today, which is basically a layer on top of WebSocket that not only adds compatibility for older browsers, but adds a lot of features, like the ability to send arbitrary events or automatic reconnection or multiplexing, which are very, very useful when you’re developing actual applications. Like for example, if you wanted to add a chat capability to your application or if you wanted to add a real-time news feed or a functionality like that.

JAMISON:

So, I’ve used Socket.IO a fair amount. I’ve never used just the raw WebSocket protocol. Can you talk a little bit about what the base protocol is? And then maybe it’ll make more sense about all the features that Socket.IO provides on top of that.

GUILLERMO:

Yeah. So, WebSocket is basically, imagine if you were only sending a message event on Socket.IO. In fact, you can basically accomplish what WebSocket does very easily. You just ignore any other event and you just, from back and forth, from server to client and client to server, you’re always sending the same type of event, a message event. And the WebSocket protocol is designed to add really minimal framing. So, what this means is that when you send data from browser to server or server to browser, what surrounds the data that you’re actually sending, like for example user input or I don’t know, you’re sending time or whatever, or a JSON data structure, basically WebSocket only adds an identifier of the message type which has the length of the message, and that’s it.

Now, let’s compare that with HTTP. When you send a request, the user data or your data or your JSON data is usually surrounded by tons of bytes, which obviously is not a lot in the capabilities of our computers and networks and whatever. But it does add a lot of overhead. So, you’re sending the user agent and the content type and all this stuff. WebSocket basically resets us back to a raw TCP socket with a very minimal protocol whose main goal is to be compatible with HTTP.

So, the WebSocket handshake which is what occurs when you open a WebSocket connection, is basically saying, “Hello. I want to upgrade and this is an HTTP header, upgrade to WebSocket.” And then the server can reply, “Okay.” WebSocket handshake, they exchange some security secrets, and then the connection is basically yours. You can send packets back and forth with very minimal framing. Now, the story has gotten a lot more complicated though, because the one improvement that WebSocket made, which was minimalistic framing, can actually be extremely useful for any type of HTTP request.

And that’s what Google realized with their SPDY protocol, S-P-D-Y. And that’s basically the shell of HTTP 2.0. So, what they realized is for example, if you establish a connection with the server and you start making a lot of requests, like regular HTTP requests, they’re going to all include a lot of information that’s common to that session. Like for example, the user agent. Why are you sending it 20 times over the lifetime of the user interaction with the server if we can send it once? Or even better, the protocol can already have a dictionary of user agents and then we can refer to it with just one byte. This is basically the idea behind header compression.

JAMISON:

That’s cool.

GUILLERMO:

There is a gzipped dictionary that’s already built in that’s protocol-aware. And obviously, there have been a lot of debates about how SPDY impacts future developments and how it breaks certain things. But it’s extremely good at just making any sort of request a lot faster. So, their analysis shows that a lot of the top hundred websites, if they just flip the switch to enable SPDY in their backends, which is a dramatically simpler task than refactoring your entire application for a new protocol, they found that in the worst case scenario, there is a 30% improvement and the best case scenario is 70% improvement the last time I checked.

So, WebSocket which used to be its own dedicated TCP socket is now going to be started to be layered over this SPDY multiplexed connection. So, that’s why I think it’s not so useful to try to keep up with how the protocol works, just because even in the last few years it’s changed dramatically. And that’s what we tried to do with Socket.IO. We try to hide all this complexity and always try to make it as fast as possible for whatever transport is actually carrying the user data. And we let users only care about their obligational, or whatever gets closest to the application, which in this case is the event emitter, the ability to send different types of data back and forth.

JAMISON:

That was a really long and really good answer.

[Chuckles]

GUILLERMO:

Sorry.

JAMISON:

No, that was amazing. That makes a lot of sense. Socket.IO is the framework that abstracts away the changing details of WebSockets. So, you get all the performance benefits that come along with updates to the spec without having to update all your application code basically.

GUILLERMO:

Exactly.

CHUCK:

So, you keep mentioning multiplexing, which to me means you’re sending data over multiple channels. How do you generally make the best use of that? Or what is a good use case for it?

GUILLERMO:

Yeah. That’s a good question. Usually, I think about multiplexing in terms of, it’s similar to how when you include an iframe with Disqus or you include the Facebook like button and you don’t care about the implementation details of that connection over to their servers. It’s similar, you can apply a similar concept to your application where you don’t care about how many TCP sockets things are going over or you don’t care about how your data’s being managed. But each piece of your application thinks that they’re getting their own dedicated socket. And that’s cool, because you can write a lot more modular code that’s just as efficient as if it was a one monolithic thing.

So, basically you can write different parts of your application that establish… you can have 20 sockets in one page. But they’re being multiplexed. And different parts of your codebase think they have ownership over the entire channel, which is effectively what’s happening with WebSocket now, too, with SPDY. So, we give you that guarantee, even if SPDY’s not enabled or even if you don’t know what SPDY is. The key thing is that we can give you the best possible performance without trading off the simplicity of part of the codebase thinking, “Oh, I have this entire communication channel for myself.”

CHUCK:

So, one other question I have, and this is something that I’ve seen usually when I see somebody demonstrating sockets or demonstrating a use for Socket.IO in particular. They’re talking about it as, “You can do this or you can do polling.” So, besides the things that you brought up where you send the user agent every time and things like that, I guess what are the tradeoffs? Are there cases where you’d want to do polling? Or [inaudible] just completely [inaudible].

GUILLERMO:

That’s an excellent question, and I’ve been meaning to write about it extensively, because polling actually makes a lot of sense in certain scenarios. For example, back when we did the first Node.js hackathon with Joyent, I remember that they created an amazing panel for showing off the details of how their teams were doing. And I remember that we started of course implementing it with Socket.IO, or they started implementing with Socket.IO and I was just simply advising them, because obviously that was the hot thing about Node.js and they wanted to show it off. But then when the competition actually started, we realized that it was so much data coming in that it didn’t actually even make sense to send it in real-time to every client.

This is something that obviously it doesn’t happen always. But in certain applications, it might be too much to send all the data in real-time to a frontend. So, in those cases, if you get a snapshot of the data every ten seconds, the user doesn’t have a meaningful disadvantage over getting it in 100 milliseconds every second. So, there are a few scenarios where polling works. Now that said, I think there is no scenario where it actually is better. So, it’s good enough in that case because you can still throttle data from the server and you have a lot more control when the server is sending the data to the client. And for example, there were actually some parts of that one frontend that did have a lot of frequent updates that made a lot of sense to send in real-time. And so, they traded that off a little bit.

So, I think it’s a good enough solution in a lot of cases. But what I usually point to is the fact that in the design of most applications that we design these days, the server is the source of truth of the data. So, it never makes sense to make an extra roundtrip for the client to ask the server, “What’s the truth?” or “What’s the latest?” whereas the server knows, and the server knows who’s interested in it, because it keeps track of what clients have open in the page. So, there is no situation that I can think of where polling is actually better. But there are some situations where if you carefully examine the pros and cons, especially as far as implementation time and implementing it in your stack or changing too much of your codebase, polling could be good enough.

That’s why what I always say is, “Really, it’s all about the user experience.” It’s all about making the UI or the frontend eventually consistent, not having to make the user press a button to get that consistency in the data. So, whatever means you use to accomplish that, they’re all better than not doing it at all. [Chuckles] So, if you’re polling to make the data be up to date on behalf of the user end, you don’t have to have them pull to refresh on mobile or press a button on the browser, that’s better. Now, the most optimal solution, and this is the solution that I obviously try to aim for, is obviously a server pushing data to the client because that’s where the data lives. And the server can be the most efficient way of spreading that data by means of pushing.

JAMISON:

So, I have a generic question about sockets and push in general, or sorry WebSockets and push in general. There’s a lot of knowledge and resources out there about how to scale standard servers that take POSTs and GETs and stuff like that. How does that change when you’re trying to scale WebSockets or a solution where the server pushes data? Do you use different techniques or are they all the same?

GUILLERMO:

The technique that is most common is generally the same one that’s been applied for regular HTTP, which is you want to load balance the connections. There is a caveat which is for polling. Most load balancers have to be configured to keep all the polling requests on the same box, which is known as sticky load balancing. But the fundamental technique is the same. Something to keep in mind is that you always have to look at the fault tolerance side of things. So, when you’re writing a real-time application, you have to consider things like disconnections and reconnections. And so, the same caveats that go for any [greater] web application, so for example message retrying.

So for example, Facebook and others do a really good job at keeping confirmations or acknowledgements of the messages so that if a certain message doesn’t make it through, they retry it on behalf of the user. And if past a certain number of retries, still it fails, you have to communicate with the user that that one message didn’t get delivered. So, something to keep in mind is that even though the scalability doesn’t change that much, for real-time applications, you do have to think about this concept of communicating the state of the connection to the user. In particular, as far as, “Oh, the app is offline. We’ll retry these messages later,” or situations like that.

So, it does open a series of new problems to examine. But the scalability is pretty much the same as most applications already. The main difference sometimes is that you decide to keep a state associated with the connection. And then you can, just like sessions in most web frameworks, you can keep the state in something like Redis or MongoDB. And then when they use reconnects, you can use some token to resume that session. But other than that, it’s pretty similar.

JAMISON:

That makes sense. You mentioned the complexities that come with managing connection state. So, is that something that Socket.IO takes care of for you or do you have to handle that in your application as well?

GUILLERMO:

So, it’s something that we definitely provide a lot of help with. So, we have middleware that makes it really easy for people to keep track of a session and to do authentication. We have a special type of error event to do basically, to communicate from the server to the client that something has gone wrong, which makes it really, really easy to do authentication and other type of error transmission. We used to, we sort of tried to do some experiments with at the core level introduce some hooks to do storage of data or persistence. But it’s just a problem that is really hard to generalize.

I think this is what most ORMs and abstractions like that have found when they try to abstract over too many different types of databases. It’s usually very hard to do successfully. So, what we’re going to move into soon is different types of persistent solutions on top of Socket.IO that are not generally available for every sort of database, but make persistence and state management for different types of databases really easy to do. But that’s not going to live on the core framework. That’s going to be something that you use on top of it.

And that’s why I was mentioning earlier that multiplexing comes in really handy, because you say, you can mount, we can call mounting it, a subsystem that adds more features on like, /something. And then a certain part of your web application is going to connect to /something and that works in a certain way. And then if you want to send Socket.IO events separately, you connect to /something-else. So, that’s where the multiplexing comes in really handy.

But yeah, state is definitely a very, very, very interesting problem. Persistence is a very, very interesting problem, too. And it’s very common to every web application that we develop, with exceptions, maybe an IRC client. It’s very desirable to always have persistence and history and queues and building blocks like that.

JAMISON:

That’s probably why all the demos are make an IRC client, because you get to skip all the hard stuff.

[Chuckles]

GUILLERMO:

So, that’s something that I notice a lot, even the chat clients. To get chat done really, really well, I was sort of hinting at that earlier. You have to do a lot. You have to do retrying. You have to do acknowledgements. You have to do, for example sometimes you could get duplicates. You have to do reconciliation with the server when you disconnect and you’re offline for a while. And then when you resume the session, you have to get everything in between. Presence is another thing that seems easy when you first approach it. But to do it on a, for example, multi-device way, it’s not as simple to do.

It’s a lot of the problems that have already been widely researched though. For example, XMPP tried to solve all of those problems [chuckles] in one protocol. So, that speaks to why maybe they didn’t get as much adoption. That’s why I intend to keep Socket.IO really simple and really approachable, even if the applications that we have on the Get Started demos are not going to be 100% perfect. And actually, even on the Get Started chat that I recently created, I mentioned as homework a lot of different tasks that people could do to improve them. But to do everything perfect, we can’t do it all in one module. So, that’s why we’re going to have different, really good companions to Socket.IO that are going to make all those tasks easier.

JAMISON:

It’s almost like the worse is better philosophy, not that Socket.IO is worse, but…

GUILLERMO:

[Chuckles] I think it’s [inaudible]…

JAMISON:

by being very approachable…

GUILLERMO:

I think simple is better when it comes to open source, especially because a lot of projects have really big learning curves and tons and tons of features to learn. That’s why keeping the core, that’s I think one of the major things we’ve accomplished in 1.0, deciding okay, this is it for the API for 1.0 and for the rest of the branch. And we can now focus on, for example, there have been tons of contributions of libraries for almost every language and framework known to man. And we can only do that when we say, “Okay, this is it. This is how many features we’re going to have in 1.0.”

JAMISON:

Sure. So, can you talk a little bit about Engine.IO? I know it’s somehow related to Socket.IO but I don’t understand what it is.

GUILLERMO:

So, it’s basically transport [inaudible].

JAMISON:

Okay.

GUILLERMO:

Which can be swapped with WebSocket directly if you wanted. So, it’s essentially the same API as WebSocket, almost like a shim. But it has support for model transport, like polling and JSONP and WebSocket itself. So, it’s basically a compatibility layer. If you want to use WebSocket in a really reliable way, you probably need to not assume that the network or the browser or the device is going to support WebSocket. So, what we do instead with Engine.IO is we use Ajax, like Ajax polling. And then if WebSocket works, we upgrade to it. So, it’s basically a very reliable way of establishing a socket connection.

CHUCK:

Are there any security concerns that you need to have that are different from just a regular HTTP connection?

GUILLERMO:

I think the common principles always apply. You have to be careful about authentication. You have to be careful about cross-domain. Some people have expressed concern with JSONP as a transport, but that applies to every time you use JSONP you’re basically evaluation code directly in the page that comes from the server, which is different from just evaluation, or I’m sorry parsing a JSON response.

But other than that, it’s very similar to everything you do for… sometimes, I remember in the first year of Socket.IO I would go to conferences or workshops and I would start live coding an example and the first thing that people would do when they would notice that for the sake of practicality and speed on the tutorial I would use for example innerHTML. And immediately, someone in the audience would troll the live demo and do insert a string with alert.

JAMISON:

[Chuckles]

GUILLERMO:

So, it’s basically the same principles. Sometimes I would say I’ve seen that people sort of “forget” them when they are creating real-time applications just because it’s something new. But really, you have to always have those considerations in mind.

JAMISON:

So, what’s in store for the future of Socket.IO? You mentioned that you nailed down the feature set for 1.0. What’s after that’s done?

GUILLERMO:

So, in the most immediate future we’re going to be focusing on reliability and speed. We have some, 1.1 is going to be pretty awesome in that we have a lot of nice improvements in terms of reliability and a smaller build actually for browsers. And I think in one situation we’re going to reduce even one roundtrip. So, it’s going to be cool in that you just drop it in and it’s better and faster. So, for the time being we’re going to continue to do that in the 1.0 branch.

As far as 2.0, we’re probably going to do what jQuery did in that dropping support for very old browsers will make sense. But we’re not going to drop support in that it’s going to be impossible to support them. We’re just not going to make the default build work for things like IE 6 or IE 7, and potentially IE 8. So, you’re going to get a smaller build by default. And it would still be possible to build in for supporting older browsers, just because like I mentioned earlier, Engine.IO to Socket.IO exposes basically the WebSocket API.

So, now that we did all that work we don’t have to worry about any sort of, almost no browser compatibility problems. And we also have very robust tests in place that span all the mobile devices that we support and all the versions of IE. So, to us it’s not a problem to support older browsers. But I would like to see a very, very lean build for modern browsers. So, that’s definitely in the scope for 2.0.

And like I mentioned, we’re going to be focusing a lot on the other problems that people normally have to make them really easy with Socket.IO. So, three of them that I can mention right now are, one is peer-to-peer, making it really easy to send events with any arbitrary data just like with the same Socket.IO guarantees between peers directly, with reconnection. So basically, imagine if we apply all the same Socket.IO principles to peer-to-peer connectivity. And even with sever fallback. So, that’s one thing that’s in scope.

Another one is persistence, and another one is presence. So, persistence means basically like I mentioned earlier, like getting updates over a data set that is beyond the scope of the process memory that you’re connecting to. And presence relates to making it really easy to say you’re online, you’re offline, you’re online but you have two active sessions, one from your mobile phone and one from the browser. So, we’re just going to make that extremely easy to do, and to plug into your Socket.IO server. So, those are the main things that are on my roadmap. But obviously, we want to maintain a steady pace of minor releases as well.

JAMISON:

Gee, I have a change of subject.

GUILLERMO:

Alright.

JAMISON:

And you may be biased because you wrote an open source push implementation. But what do you think of all the third-party providers like PubNub or Pusher or Firebase that are doing data synchronization stuff?

GUILLERMO:

Oh, I think it’s fantastic. This is hopefully so big that we have dozens of those and we have tons and tons of frameworks. The main reason is, like I was mentioning earlier, it comes into UI and UX. We want people to get their data from the server faster. That means not moving your mouse over to the toolbar and clicking refresh. And that also means not doing pull to refresh every second. So, I think it’s such a fundamental thing to me. It’s such an important thing. I want every application to act like this. There is never a good reason to, well maybe there is a few, but normally a UI has to be self-updating. And that’s how mostly I’ve come to define real-time applications.

Like I was mentioning earlier, if you’re polling that’s fine. It’s a significant improvement over not doing it and not showing data updates in real-time. So hopefully, there are tons of companies and frameworks that have this as a motivating principle and make it easier for users and companies and everyone else to get there.

As far as how all those, all those that you mentioned have differences in the technical level. That’s why beyond that, I can’t say, “Oh, this one or that one, or this one, this or that.” But they’re all really good. In fact, PubNub wrote a great article on how they analyzed the Google trends and basically the search data for all the terms of this family of concepts, like WebSocket and Socket.IO and push and all this. And it was showing basically an exponential growth in interest. So, when you have a situation like that where so many people and companies are interested in these technologies, you’re not going to have one solution for everybody.

That’s why also as part of our work right now, like you mentioned we are all about open source, part of what we’re doing right now is trying to bring the entire community together. There’s tons of clients for Objective C and now Swift. And so, bringing the whole ecosystem together to make the code accessible to everyone is also one of the priorities.

CHUCK:

Do sockets work nicely with some of the frontend frameworks like Ember or Angular? Do they require a library?

GUILLERMO:

Yeah. [Inaudible] What I’ve been noticing lately is Angular has a great implementation of a component to hook Socket.IO. So, I’ve been noticing more than anything else, a really big [op ticket] how… It’s almost become a stack where people use Angular and Socket.IO together a lot. I myself haven’t looked at it. I haven’t used it yet. But it’s something that I would definitely try, because it seems like people are having a lot of success in building the entire application in this way, with Angular.

But basically any framework that makes it really easy to do data binding is going to play really well with Socket.IO. Or even if you’re writing one component for an otherwise not real-time web app and if you’re doing it with Socket.IO and jQuery, that’s also going to work well. But in general, I think frameworks are going to help with a lot of other issues like offline support and routing. And so, in general it’s very useful to have them in your toolset.

JAMISON:

So, with Angular you just modify the data and the digest will take care of updating your stuff? It seems like it shouldn’t be too much work to put it in. If you’re using something like Ember Data, I

imagine you’d have to do some trickery because it has central place where it expects all the data to come from. But I know I’ve seen blog posts about using Socket.IO with Ember.

GUILLERMO:

Cool.

JAMISON:

I just haven’t read them.

CHUCK:

[Chuckles]

JAMISON:

I’m confessing.

GUILLERMO:

[Chuckles]

CHUCK:

Alright.

JAMISON:

Well, do you have any questions that you wish we would have asked you? Any softballs you want us to serve up?

GUILLERMO:

[Laughs] No. Actually, there have been great questions in this podcast, specifically the ones pertaining to scalability but also the polling one was really interesting because I haven’t had an opportunity to talk about that one funny anecdote with the first Node.js example that we did. But yeah, so far, so good.

CHUCK:

So, one thing that does come to mind speaking of scaling is that a lot of times you wind up with the load balancer that sits between your app servers and your web browser. So, does it play nicely over those or does it have to get some kind of direct connection to the server?

GUILLERMO:

No, it plays very nicely with those. At Cloudup we use Nginx as a load balancer. It has remote address sticky load balancing. I’ve seen people do it even on iptables where you can a bunch of processes running and then a set of iptables rules for matching ports with connections. That’s what Zendesk does for scaling Socket.IO. But I’ve also seen a lot of successful usage of HAProxy, Vagrant, ELB, the Elastic Load Balancer, other services but with a certain configuration works as well. In general, it’s just fairly easy to do. There are some issues with Heroku right now. But they’re working on addressing them. Like I said, it’s pretty standard.

CHUCK:

Alright. So, should we do the picks?

JAMISON:

Sure, I’m ready.

GUILLERMO:

Yeah.

CHUCK:

Alright, Jamison. What are your picks?

JAMISON:

I have three picks. One is a SlideDeck on CSS. CSS is a thing that I wish I was better at. And this one would make me better at it if I knew all the stuff in here. It’s a presentation by my coworker and friend Alma. He does some crazy trickery. There’s one where he does, he creates as periodic table in CSS and then has all these hover effects. And it’s all pure CSS and uses some nth child magic to make sure that all the different groupings in the periodic table are colored correctly and that the hover effects will move the hover into the right place so it doesn’t obscure any elements that are close by and things like that. It’s pretty nuts.

My second pick is just a thing I saw posted on Twitter in The New Yorker magazine. And it’s just a short story about an immigrant from the 1900s that moves to New York and then has a Rip Van Winkle thing where he falls asleep for 100 years and then wakes up in current day New York and just makes his way in the city full of hipsters. It’s pretty funny.

And then my last one is a thing that I think I’ve picked a few times. Well, I’ll pick it again because Guillermo’s here. It’s a blog post you wrote called the ‘Need for Speed’ just talking about some of his ideas about real-time applications and how to make things fast. It’s a really good read if you haven’t read it yet.

GUILLERMO:

Thank you.

CHUCK:

Awesome. I’ve got a couple of picks. I picked these books on all of my shows but I really liked them. So, I’m going to pick a couple of them in here. One of them is called ‘QBQ! The Question Behind the Question’. And it talks about personal responsibility. It’s actually a really short book, but it really, I don’t know, it really inspired me. So, I think everybody should go and read it.

Another book that I got from the same list was ‘The Go-Getter’. And it’s a story with a moral, so sort of a fable I guess. But it goes through and really talks about what it means to be a go-getter. And I don’t know, I really liked it and really found it inspiring, too.

And then the last book is ‘Rhinoceros Success’. And if you don’t like books that have a metaphor that take it too far to the point where they get a little bit hoaky, then don’t read that one. But I thought it was really good. I thought the overall message of the book was right on point. And I really liked it. So, those are my picks. Guillermo, what are your picks?

GUILLERMO:

I’ll go with three as well. The first one is a project that came out recently, I think maybe a week ago. It’s called p5.js. You guys might have even talked about it. So, it’s basically Processing, the language, that makes it really easy to do any sort of interactive are or graphic, interactive graphics. Before I think it was for [inaudible] and then it was ported to JavaScript by John Resig. So, p5 is basically what would Processing look like if it were started today with JavaScript, with HTML5, et cetera?

And I love it not only because I think it makes it really easy for people to get into programming because it’s so visual. But also it shows the versatility of JavaScript and how you can create higher level domain-specific languages very naturally. It basically reminds me of Mocha, what TJ did for testing, introducing all those globals and just making it really expressive, almost like English to write a test. So, this does the same but for graphics. So, check it out, p5.js.

The next one is also on the same note of getting more people to learn and get interested in computer science. There’s a great post by my coworker, Beau Lebens on why JavaScript is the next programming language you should learn, or the first programming language you should learn. It’s a really great succinct blog post.

And finally, it’s a Twitch.tv channel called FishPlaysPokémon.

[Laughter]

GUILLERMO:

I think it’s an awesome display of computer vision and just badass ideas being implemented. [Chuckles] I think it’s funny how we got, I think 20,000 people to watch that concurrently. And someone that has written a collaborative Pokémon emulator online, you can check it out on weplay.io, it’s really fun to see.

And actually, that also inspired an idea that someone should do. So, on the Socket.IO homepage there is an eight-line example of how to get events for Twitter searches. And then they get emitted with Socket.IO to the client. So, it’d be really fun to make a game where Twitter plays Pokémon by using a hashtag or mentioning someone. And I think it would be maybe 15 lines of code and be really funny to watch. So, those are my three picks.

JAMISON:

I think the fish is dead.

GUILLERMO:

I think some people reported that he was dead, yeah. But then when I first started he was dead, then he came back alive.

[Laughter]

GUILLERMO:

[Inaudible] dead fish.

JAMISON:

Oh wait, no. I see it. Fish is alive.

CHUCK:

Alright.

JAMISON:

This is incredible.

CHUCK:

I’ll have to go check it out in a second here. I don’t want the audio to play through the podcast. That was really cool. Thanks for coming, Guillermo.

GUILLERMO:

No problem. Thank you.

JAMISON:

Thank you. This was great.

[Working and learning from designers at Amazon and Quora, developers at SoundCloud and Heroku, and entrepreneurs like Patrick Ambron from BrandYourself, you can level up your design, dev, and promotion skills at Level Up Con taking place October 8th and 9th in downtown Saratoga Springs, New York. Only two hours by train from New York City, this is the perfect place to enjoy early fall and Oktoberfest while you mingle with industry pioneers in a resort town in upstate New York. Get your ticket today at LevelUpCon.com. Space is extremely limited for this premium conference experience. Don’t delay. Check out LevelUpCon.com now.]

[This episode is sponsored by MadGlory. You’ve been building software for a long time and sometimes it’s get a little overwhelming. Work piles up, hiring sucks, and it’s hard to get projects out the door. Check out MadGlory. They’re a small shop with experience shipping big products. They’re smart, dedicated, will augment your team and work as hard as you do. Find them online at MadGlory.com or on Twitter at MadGlory.]

[This episode is sponsored by RayGun.io. If at any point you application is crashing, what would that cost you? Lost users, customers, revenue? RayGun is an essential tool for every developer. RayGun takes minutes to integrate and you’ll be notified of your software bugs as they happen with automatic notifications, a full stack trace to detect, diagnose, and fix errors in record time. RayGun works with all major mobile and web programming languages in a matter of minutes. Try it for free today at RayGun.io.]

[Hosting and bandwidth provided by the Blue Box Group. Check them out at Bluebox.net.]

[Bandwidth for this segment is provided by CacheFly, the world’s fastest CDN. Deliver your content fast with CacheFly. Visit CacheFly.com to learn more.]

[Do you wish you could be part of the discussion on JavaScript Jabber? Do you have a burning question for one of our guests? Now you can join the action at our membership forum. You can sign up at

JavaScriptJabber.com/jabber and there you can join discussions with the regular panelists and our guests.]

JavaScript Jabber 122 JSJ Socket.IO with Guillermo Rauch
JavaScript Jabber 007 JSJ Online Resources for Javascript Developers
JavaScript Jabber 005 JSJ Javascript Objects
JavaScript Jabber JSJ 329: Promises, Promise.finally(), and Async/await with Valeri Karpov
JavaScript Jabber 004 JSJ Backbone.js with Jeremy Ashkenas
JavaScript Jabber 003 JSJ Build Tools
JavaScript Jabber 021 JSJ Weapons of Choice
JavaScript Jabber JSJ 280: Stackblitz with Eric Simons and Albert Pai
JavaScript Jabber JSJ 328: Functional Programming with Ramda with Christine Legge
JavaScript Jabber 025 JSJ Require.js with James Burke
JavaScript Jabber JSJ 358: Pickle.js, Tooling, and Developer Happiness with Anatoliy Zaslavskiy
JavaScript Jabber JSJ 326: Conversation with Ember co-creator Tom Dale on Ember 3.0 and the future of Ember
JavaScript Jabber JSJ 413: JavaScript Jabber at RxJs Live
JavaScript Jabber 064 JSJ Ember Tools with Ryan Florence
JavaScript Jabber JSJ 325: Practical functional programming in JavaScript and languages like Elm with Jeremy Fairbank
JavaScript Jabber 041 JSJ Single Page Applications
JavaScript Jabber Simplifying Full-Stack Dev with the "Boring JavaScript Stack" and Sails Framework - JSJ 621
JavaScript Jabber Mastering Back-End Functionalities and Development with AWS Amplify - JSJ 619
JavaScript Jabber JSJ 324: with Kent Beck
JavaScript Jabber Exploring AI Impact on Code Generation and Quality Metrics - JSJ 618
JavaScript Jabber Unlocking Vue and Nuxt Potential: New Tools, Best Practices, and more - JSJ 652
JavaScript Jabber Inside the World of React: Server Components, Unidirectional Data Flow, and Frameworks - JSJ 617
JavaScript Jabber JSJ 321: Babel and Open Source Software with Henry Zhu
JavaScript Jabber 073 JSJ React with Pete Hunt and Jordan Walke
JavaScript Jabber Iterating on Open Source - JSJ 615
JavaScript Jabber JSJ 320: Error Tracking and Troubleshooting Workflows with David Cramer LIVE at Microsoft Build
JavaScript Jabber Dev Dilemmas: TypeScript Triumphs and Quirks of JavaScript Arrays - JSJ 614
JavaScript Jabber Optimizing SQL and ORM Practices for High-Performance Applications - JSJ 650
JavaScript Jabber JSJ 339: Node.js In Motion Live Video Course from Manning with PJ Evans
JavaScript Jabber The Future of Authentication in JavaScript: An Inside Look into Passport JS with Jared Hanson - JSJ 613
JavaScript Jabber The Rise of No Code: A Deep Dive into Toddle's Revolutionary Web App Platform - JSJ 612
JavaScript Jabber Bit: Paving the Way for Component Management - JSJ 610
JavaScript Jabber JSJ 318: Cloud-Hosted DevOps with Ori Zohar and Gopinath Chigakkagari LIVE at Microsoft Build
JavaScript Jabber Next-Level Web Performance with Patrick Meenan - JSJ 608
JavaScript Jabber Partytown with Adam Bradley - JSJ 550
JavaScript Jabber Mastering ORM with TypeScript - JSJ 606
JavaScript Jabber JSJ 314: Visual Studio Code and the VS Code Azure Extension with Matt Hernandez and Amanda Silver LIVE at Microsoft Build
JavaScript Jabber What has Changed with htmx 2.0 with Carson Gross - JSJ 604
JavaScript Jabber Discovering ElysiaJS and The Duality of TypeScript and JavaScript - JSJ 609
JavaScript Jabber View Transitions API with Noam Rosenthal - JSJ 602
JavaScript Jabber JSJ 310: Thwarting Insider Threats with Greg Kushto
JavaScript Jabber From Learning New Languages to Learning New Technologies - JSJ 629
JavaScript Jabber Accessibility in Component Libraries with Maya Shavin - JSJ 601
JavaScript Jabber 131 JSJ Conferences & Meetups with Dave Nugent
JavaScript Jabber JSJ 309: WebAssembly and JavaScript with Ben Titzer
JavaScript Jabber JSJ 270 The Complete Software Developers Career Guide with John Sonmez
JavaScript Jabber Unraveling the CSS Revolution, Podcast Growth Tactics, and More - JSJ 600
JavaScript Jabber Redwood JS in Action with Tom Preston-Werner - JSJ 599
JavaScript Jabber Exploring the True Measure of User Experience: Core Web Vitals & Beyond - JSJ 598
JavaScript Jabber JSJ 308: D3.js with Ben Clinkinbeard
JavaScript Jabber 217 JSJ The Now Project with Guillermo Rauch
JavaScript Jabber 226 JSJ Test Doubles with Justin Searls
JavaScript Jabber 208 JSJ MS Office with Jeremy Thake
JavaScript Jabber What if your JavaScript Validations Looked like Tests? - JSJ 597
JavaScript Jabber Embracing Web Standards with Owen Buckley - JSJ 626
JavaScript Jabber Is JavaScript on the Backend a Mistake? - JSJ 596
JavaScript Jabber JSJ 374: CosmosDB with Steve Faulkner LIVE at Microsoft BUILD
JavaScript Jabber Why Should You Get Into The Web3 World - JSJ 595
JavaScript Jabber JSJ 307: Apollo with Peggy Rayzis
JavaScript Jabber Svelte 5: Compiler, Signals, and Web App Performance - JSJ 627
JavaScript Jabber JSJ 305: Continuous Integration, Processes, and DangerJS with Orta Therox
JavaScript Jabber The Evolution of Qwik - JSJ 594
JavaScript Jabber 092 JSJ The MEAN Stack with Ward Bell and Valeri Karpov
JavaScript Jabber JSJ 402: SEO for Developers with Vitali Zaidman
JavaScript Jabber Introducing The B2B SaaS Starter Kit - JSJ 593
JavaScript Jabber The CSS Universe with Austin Gil - JSJ 592
JavaScript Jabber 189 JSJ PureScript with John A. De Goes and Phil Freeman
JavaScript Jabber Progressive Enhancement with Elliott Johnson - JSJ 591
JavaScript Jabber Things Coming Down the Pipe From TC39 - JSJ 590
JavaScript Jabber JSJ 303: Test Coverage Tools with Ben Coe, Aaron Abramov, and Issac Schleuter
JavaScript Jabber Million.js with Aiden Bai and Tobiloba Adedeji - JSJ 589
JavaScript Jabber 121 JSJ Broccoli.js with Jo Liss
JavaScript Jabber How to Build Peer-to-Peer Mobile and Desktop Apps with Socket Supply - JSJ 588
JavaScript Jabber What It Takes To Be A Web Developer: Part 2 - JSJ 587
JavaScript Jabber Streamlining AI Integration - JSJ 616
JavaScript Jabber What It Takes To Be A Web Developer: Part 1 - JSJ 586
JavaScript Jabber Defining and Learning Web Fundamentals - JSJ 585
JavaScript Jabber JSJ 302: Evaluating Web Frameworks with Kitson Kelly
JavaScript Jabber Find Out More About Barry Pollard - BONUS
JavaScript Jabber React Server Components: Part 2- JSJ 583
JavaScript Jabber React Server Components: Part 1 - JSJ 582
JavaScript Jabber 151 JSJ Getting Started with a Career in Web Development with Tyler McGinnis
JavaScript Jabber Making AI Accessible for Developers - JSJ 641
JavaScript Jabber Overcoming JavaScript Load Issues: Import Maps and Performance Enhancements - JSJ 643
JavaScript Jabber JSJ 435: Form.io with Travis Tidwell
JavaScript Jabber JSJ 298: Angular, Vue and TypeScript with John Papa
JavaScript Jabber Find Out More About Brad Westfall - BONUS
JavaScript Jabber JSJ 248 Reactive Programming and RxJS with Ben Lesh
JavaScript Jabber 169 JSJ Property-based Testing (QuickCheck) with Zach Kessin
JavaScript Jabber SolidStart with Ryan Carniato - JSJ 581
JavaScript Jabber JSJ 438: You Don't Know JS Yet with Kyle Simpson (SPECIAL ANNOUNCEMENT at the End)
JavaScript Jabber Cross Platform App Development with Simon Grimm - JSJ 580
JavaScript Jabber JSJ 297: Scrollytelling with Russell Goldenberg and Adam Pearce
JavaScript Jabber JSJ 434: Understanding and Using ES Modules in Node with Gil Tayar
JavaScript Jabber JSJ 296: Changes in React and the license with Azat Mardan
JavaScript Jabber JSJ 294: Node Security with Adam Baldwin
JavaScript Jabber 134 JSJ Quilljs with Jason Chen
JavaScript Jabber 237 JSJ CLls - Ember Angular and React with Tracy Lee
JavaScript Jabber 074 JSJ Grunt with Ben Alman
JavaScript Jabber JSJ 311: Securing Express Apps with Helmet.js with Evan Hahn
JavaScript Jabber JSJ 288: TypeScript with Amanda Silver
JavaScript Jabber 170 JSJ RabbitMQ with Derick Bailey
JavaScript Jabber 173 JSJ Online Learning with Gregg Pollack
JavaScript Jabber Simplifying Development with Deno - JSJ 625
JavaScript Jabber 194 JSJ JavaScript Tools Fatigue
JavaScript Jabber 196 JSJ Tabris.js with Jochen Krause and Ian Bull
JavaScript Jabber 200 JSJ EPISODE 200!!!
JavaScript Jabber 205 JSJ Shasta with Eric Schoffstall
JavaScript Jabber 006 JSJ Chrome Dev Tools with Paul Irish
JavaScript Jabber 211 JSJ Ember and EmberConf with Michael North
JavaScript Jabber 216 JSJ Angular with Rob Wormald Live from Microsoft Build 2016
JavaScript Jabber 220 JSJ Teaching JavaScript with Kyle Simpson
JavaScript Jabber 223 JSJ WebStorm with Dennis Ushakov
JavaScript Jabber 197 JSJ Auth0 with Kassandra Perch
JavaScript Jabber JSJ 466: Infrastructure as Code with Christian Nunciato
JavaScript Jabber JSJ 467: The Joy of JavaScript with Luis Atencio
JavaScript Jabber JSJ 286: Creating a CSS-in-JS Library from Scratch and Emotion with Kye Hohenberger
JavaScript Jabber Being a New Developer with Diego Moura - JSJ 553
JavaScript Jabber Exploring Local-First Applications and Data Synchronization Challenges - JSJ 654
JavaScript Jabber JSJ 432: Internet of Things (IoT) with Joe Karlsson
JavaScript Jabber JSJ BONUS: Cloud Services and Manifold with Matthew Creager and Peter Cho
JavaScript Jabber Understanding, Confidence, and Humility in Web development - JSJ 655
JavaScript Jabber JSJ 283: A/B Testing with Nick Disabato
JavaScript Jabber JSJ 348: EnactJS with Ryan Duffy
JavaScript Jabber Exploring Local-First Applications and Data Synchronization Challenges - JSJ 654
JavaScript Jabber Stimulus and Turbo in Web Development - JSJ 656
JavaScript Jabber Supply Chain Security with Stephen Chin - BONUS
JavaScript Jabber Simplifying Slinkity with Anthony Campolo
JavaScript Jabber JSJ 282: Trails.js with Scott Wyatt
JavaScript Jabber JSJ 437: Inside the Brave Browser with Jonathan Sampson
JavaScript Jabber SolidJS with Ryan Carniato - JSJ 528
JavaScript Jabber JSJ 443: All About InertiaJS with Jonathan Reinink
JavaScript Jabber JSJ 289: Visual Studio Code and Live Sharing with Chris Dias and PJ Meyer LIVE at Microsoft Connect 2017
JavaScript Jabber JSJ 281: CodeSponsor - Sustaining Open-Source Software through Ethical Advertising with Eric Berry
JavaScript Jabber JSJ 245 Styled Components and react-boilerplate with Max Stoiber
JavaScript Jabber JSJ 451: Are Software Bugs Inevitable with Ran Levi
JavaScript Jabber Qwik with Misko Hevery - JSJ 549
JavaScript Jabber JSJ 279: ES Modules in Node Today! with John-David Dalton
JavaScript Jabber JSJ 442: Breaking Into Tech with Danny Thompson
JavaScript Jabber Dan Shappir's Failed Predictions - JSJ 552
JavaScript Jabber 102 JSJ Angular and Open Source Projects with Brad Green
JavaScript Jabber To TypeScript or Not to TypeScript - JSJ 538
JavaScript Jabber 100 JSJ Centennial Episode Celebration
JavaScript Jabber JSJ 278 Machine Learning with Tyler Renelle
JavaScript Jabber JSJ 275: Zones in Node with Austin McDaniel
JavaScript Jabber 209 JSJ TypeScript with Anders Hejlsberg
JavaScript Jabber JSJ 274: Amazon Voice Services and Echo Skills with Terrance Smith
JavaScript Jabber How To Recession Proof Your Job - BONUS
JavaScript Jabber All Things TypeScript with Maina Wycliffe - JSJ 559
JavaScript Jabber 018 JSJ Agile Development
JavaScript Jabber JSJ 273: Live to Code, Don't Code to Live with 2 Frugal Dudes Sean Merron and Kevin Griffin
JavaScript Jabber Vue Courses, Top End Devs, and More... Oh, My! - JSJ 546
JavaScript Jabber JSJ 331: “An Overview of JavaScript Testing in 2018” with Vitali Zaidman
JavaScript Jabber JSJ 272: Functional Programming and ClojureScript with Eric Normand
JavaScript Jabber 043 JSJ Sinon.JS
JavaScript Jabber JSJ 271: SharePoint Extensions in JavaScript with Mike Ammerlaan and Vesa Juvonen
JavaScript Jabber JSJ 269 Reusable React and JavaScript Components with Cory House
JavaScript Jabber 065 JSJ Build Tools with Adam Hawkins
JavaScript Jabber 046 JSJ Staying Current
JavaScript Jabber JSJ 430: Learning JavaScript in 2020 with Matt Crook
JavaScript Jabber 026 JSJ Code Organization and Reuse
JavaScript Jabber 084 JSJ Node with Mikeal Rogers
JavaScript Jabber 012 JSJ Design Patterns in JavaScript with Addy Osmani
JavaScript Jabber Women on Stage and in Tech with Moran Weber - JSJ 483
JavaScript Jabber JSJ 301: CSS Grids: The Future of Frontend Layout with Dave Geddes
JavaScript Jabber JavaScript and IoT with Nick Hehr and Peter Hoddie - JSJ 545
JavaScript Jabber Even More JavaScript Features You Should Avoid - JSJ 547
JavaScript Jabber 161 JSJ Rust with David Herman
JavaScript Jabber JSJ 266 NPM 5.0 with Rebecca Turner
JavaScript Jabber JSJ 343: The Power of Progressive Enhancement with Andy Bell
JavaScript Jabber 165 JSJ ShopTalk with Chris Coyier and Dave Rupert
JavaScript Jabber 080 JSJ - Impact.js with Dominic Szablewski
JavaScript Jabber JSJ 265 Wade Anderson and Ramya Rao on Visual Studio Code
JavaScript Jabber BONUS: Start Building Video Games with Jason Weimann
JavaScript Jabber JSJ 263 Moving from Node.js to .NET and Raygun.io with John-Daniel Trask
JavaScript Jabber JSJ 429: Learning about Postman with Joyce Lin
JavaScript Jabber 079 Lo-Dash with John-David Dalton
JavaScript Jabber 070 JSJ Book Club: JavaScript Allongé with Reginald Braithwaite
JavaScript Jabber 094 JSJ BonsaiJS with Tobi Reiss
JavaScript Jabber JSJ 261 HTTP 2 with Surma
JavaScript Jabber Mentorship in Tech: Balancing Professionalism and Friendship for Maximum Growth and Accountability - JSJ 649
JavaScript Jabber 101 JSJ js-git with Tim Caswell
JavaScript Jabber JSJ 260 Practical JavaScript with Gordon Zhu
JavaScript Jabber 108 JSJ AngularJS with Igor Minar
JavaScript Jabber 105 JSJ JSConf and Organizing Conferences with Chris Williams
JavaScript Jabber JSJ 349: Agile Development - The Technical Side with James Shore
JavaScript Jabber 109 JSJ Dependency Injection in JavaScript with Vojta Jína & Misko Hevery
JavaScript Jabber JSJ 397: Design Systems with Kaelig Deloumeau-Prigent
JavaScript Jabber JSJ 259 Clean Code JavaScript with Ryan McDermott
JavaScript Jabber JSJ 258 Development in a Public Institution with Shawn Clabough
JavaScript Jabber 119 JSJ Chrome Apps with Joe Marini
JavaScript Jabber The State of WASM - JSJ 560
JavaScript Jabber Sorting through the Script (AJ vs. Dan Shappir) - JSJ 519
JavaScript Jabber Don't Let These Things Keep You From Podcasting - BONUS
JavaScript Jabber JSJ 388: Functional Programming with Brian Lonsdorf
JavaScript Jabber 107 JSJ ClojureScript & Om with David Nolen
JavaScript Jabber JSJ 338: It’s Supposed To Hurt, Get Outside of Your Comfort Zone to Master Your Craft with Christopher Buecheler
JavaScript Jabber JSJ 257 Graphcool with Johannes Schickling
JavaScript Jabber 129 JSJ BaaS with Ryan Done
JavaScript Jabber JSJ 425: The Evolution of JavaScript
JavaScript Jabber 132 JSJ MV Frameworks with Craig McKeachie
JavaScript Jabber Sentry's Impact on Web Vitals Understanding - JSJ 632
JavaScript Jabber 137 JSJ &yet with Henrik Joreteg and Phil Roberts
JavaScript Jabber 086 JSJ Ember.js & Discourse with Robin Ward
JavaScript Jabber Beyond JavaScript: Master TypeScript at Scale at SquiggleConf - JSJ 646
JavaScript Jabber Web3 with Nik Kalyani - JSJ 630
JavaScript Jabber Mastering Browser Caching with Vitali Zaidman - JSJ 490
JavaScript Jabber JSJ 256 Wordpress and Wordpress API for JavaScript Developers with Roy Sivan
JavaScript Jabber JSJ 428: The Alphabet Soup of Performance Measurements
JavaScript Jabber 164 JSJ Rendr with Spike Brehm
JavaScript Jabber 155 JSJ Webtorrent with Feross Aboukhadijeh
JavaScript Jabber 024 JSJ Strata.js with Michael Jackson
JavaScript Jabber 160 JSJ Stormpath with Robert Damphousse
JavaScript Jabber 159 JSJ Why JavaScript Is Hard
JavaScript Jabber 158 JSJ Roots with Jeff Escalante
JavaScript Jabber Preventing Fraud on Your Payment Website - JSJ 534
JavaScript Jabber Data Wrangling in JavaScript with Ashley Davis - JSJ 484
JavaScript Jabber 171 JSJ Babel with Sebastian McKenzie
JavaScript Jabber JSJ 431: Personal Branding for Developers with Morad Stern
JavaScript Jabber JSJ 255 Docker for Developers with Derick Bailey
JavaScript Jabber JSJ 389: What Makes a 10x Engineer?
JavaScript Jabber JSJ 254 Contributor Days with Tracy Lee
JavaScript Jabber 207 JSJ Growing Happy Developers with Marcus Blankenship
JavaScript Jabber JSJ Special Episode: Azure with Jonathan Carter
JavaScript Jabber Splatty-doo and Other JavaScript Features You Should Avoid - JSJ 543
JavaScript Jabber JSJ 252 The 20th Anniversary of Visual Studio with Bowden Kelly
JavaScript Jabber 142 JSJ Share.js with Joseph Gentle
JavaScript Jabber Becoming the Go-To Person in Your Technology Area - BONUS
JavaScript Jabber 190 JSJ Web Performance Part 2 with Nik Molnar
JavaScript Jabber 045 JSJ jQuery
JavaScript Jabber JSJ 251 InfoSec for Web Developers with Kim Carter
JavaScript Jabber JSJ 384: FaunaDB: Support for GraphQL and Serverless Development with Evan Weaver
JavaScript Jabber 222 JSJ Nodal with Keith Horwood
JavaScript Jabber JSJ 449: The Things Every JavaScript Developer Must Know
JavaScript Jabber JSJ 249 Loading and Optimizing Web Applications with Sam Saccone and Jeff Cross
JavaScript Jabber JSJ 246 GraphQL and Apollo with Uri Goldshtein
JavaScript Jabber 128 JSJ Famo.us with Steve Newcomb
JavaScript Jabber Typing Without Transpilation - The Beauty of JSDoc - JSJ 489
JavaScript Jabber 244 JSJ Visual Studio with Sam Guckenheimer
JavaScript Jabber 125 JSJ WebGL with Sean Griffin
JavaScript Jabber Can JAMstack do REAL Web Apps? with James Q Quick - JSJ 517
JavaScript Jabber 036 JSJ DOM Rendering and Manipulating
JavaScript Jabber 112 JSJ Refactoring JavaScript Apps Into a Framework with Brandon Hays
JavaScript Jabber JSJ 250 Celebration
JavaScript Jabber 227 JSJ Fostering Community Through React with Benjamin Dunphy, Berkeley Martinez, and Ian Sinnott
JavaScript Jabber JSJ 304: React: The Big Picture
JavaScript Jabber 243 JSJ Immutable.js with Lee Byron
JavaScript Jabber JSJ 401: Hasura with Tanmai Gopal
JavaScript Jabber JSJ 345: Azure Devops with Donovan Brown LIVE at Microsoft Ignite
JavaScript Jabber 242 JSJ Visual Studio and .NET with Maria Naggaga
JavaScript Jabber 066 JSJ Transitioning to JavaScript
JavaScript Jabber 235 JSJ JavaScript Devops and Tools with Donovan Brown and Jordan Matthiesen
JavaScript Jabber 234 JSJ JAMStack with Brian Douglas and Matt Christensen
JavaScript Jabber RPC Resurgence: From Client-Server Applications to Next.js and Meta Frameworks - JSJ 607
JavaScript Jabber JSJ 478: Browser Standards Rampage: Can We Have Nice Things?
JavaScript Jabber 241 JSJ Microsoft Docs with Dan Fernandez
JavaScript Jabber The MaxCoders Guide To Finding Your Dream Developer Job
JavaScript Jabber 240 JSJ Visual Studio Code with Chris Dias
JavaScript Jabber TC39 and Upcoming Proposals for ECMAScript (PART 2) - JSJ 533
JavaScript Jabber A Deep Dive Into Some Nooks and Crannies of JavaScript - JSJ 535
JavaScript Jabber 239 JSJ Vets Who Code with Jerome Hardaway
JavaScript Jabber JSJ BONUS: Web Apps on Linux with Jeremy Likness and Michael Crump
JavaScript Jabber 230 JSJ Node at Capital One with Azat Mardan
JavaScript Jabber Writing Change-Proof Software with Tests - JSJ 555
JavaScript Jabber Data Oriented Programming with Yehonathan Sharvit - JSJ 481
JavaScript Jabber Building a Custom Front-end Framework - JSJ 633
JavaScript Jabber 229 JSJ Elm with Richard Feldman
JavaScript Jabber Creating Your Community with Brett Haralson - JAVASCRIPT 515
JavaScript Jabber 225 JSJ Functional Programming with John A. De Goes
JavaScript Jabber 206 JSJ PostCSS with Ben Briggs
JavaScript Jabber JSJ 471: Things Every JavaScript Developer Must Know - Part 3
JavaScript Jabber 224 JSJ Cypress.js with Brian Mann
JavaScript Jabber Power Tips for Browser Dev-Tools with Craig Buckler - JSJ 492
JavaScript Jabber 219 JSJ Learning JavaScript in 2016
JavaScript Jabber JSJ 334: “Web Performance API” with Dan Shappir
JavaScript Jabber JSJ 476: Understanding Search Engines and SEO (for devs) - Part 1
JavaScript Jabber 215 JSJ ChakraCode with Guarav Seth Live from Microsoft Build 2016
JavaScript Jabber 214 JSJ Pebble with Heiko Behrens and François Baldassari
JavaScript Jabber 212 JSJ Horizon.js with Horizon.js with Michael Glukhovsky: Live from ng-conf!
JavaScript Jabber 089 JSJ The Node Security Project with Adam Baldwin
JavaScript Jabber BONUS: How to Crush Your Biggest Goals in 2021
JavaScript Jabber 210 JSJ The 80/20 Guide to ES2015 Generators with Valeri Karpov
JavaScript Jabber 192 JSJ IoT with Peter Hoddie
JavaScript Jabber 199 JSJ Visual Studio Code with Chris Dias and Erich Gamma
JavaScript Jabber 204 JSJ Free Code Camp with Quincy Larson
JavaScript Jabber JSJ 312: Hygen with Dotan Nahum
JavaScript Jabber 203 JSJ Aurelia with Rob Eisenberg
JavaScript Jabber 202 JSJ DoneJS + CanJS with Justin Meyer
JavaScript Jabber 111 JSJ The Ember.js Project with Erik Bryn
JavaScript Jabber 201 JSJ Security with Troy Hunt
JavaScript Jabber Unveiling Chrome DevTools: Network Monitoring, Cache Debugging, and Beyond - JSJ 623
JavaScript Jabber 198 JSJ 2015 Recap and 2016 Predictions
JavaScript Jabber Embracing Angular's Evolution with Santosh Yadav - JSJ 631
JavaScript Jabber JSJ BONUS EPISODE: Observables and RxJS Live with Aaron Frost
JavaScript Jabber JSJ 319: Winamp2-js with Jordan Eldredge
JavaScript Jabber Bun.js with Jarred Sumner - JSJ 584
JavaScript Jabber Practical Strategies for Web Optimization: Using Chrome DevTools - JSJ 635
JavaScript Jabber 195 JSJ Rollup.js with Rich Harris and Oskar Segersvärd
JavaScript Jabber Stories From The Trenches - JSJ 556
JavaScript Jabber An Unconventional Journey into Coding ft. Sam Sycamore - JSJ 496
JavaScript Jabber 193 JSJ Electron with Jessica Lord and Amy Palamountain
JavaScript Jabber JSJ 290: Open Source Software with Dirk Hohndel - VMWare Chief Open Source Officer
JavaScript Jabber 191 JSJ Stripe with Craig McKeachie
JavaScript Jabber 179 JSJ redux and React with Dan Abramov
JavaScript Jabber OAuth Explained - JSJ 523
JavaScript Jabber Front End Architecture - JSJ 522
JavaScript Jabber 186 JSJ NativeScript with TJ VanToll and Burke Holland
JavaScript Jabber Hydrogen and Oxygen - JSJ 539
JavaScript Jabber 183 JSJ Should I go to college?
JavaScript Jabber 228 JSJ React Native with Nader Dabit and Mike Grabowski
JavaScript Jabber Building and Distributing PWAs: Tools, Techniques, and Insights - JSJ 638
JavaScript Jabber 182 JSJ RxJS with Matthew Podwysocki
JavaScript Jabber 181 JSJ The Evolution of Flux Libraries with Andrew Clark and Dan Abramov
JavaScript Jabber Do You Have Dev FOMO? ft. Yoav Ganbar - JSJ 510
JavaScript Jabber 178 JSJ Tech Education and The Business of Running Front End Masters with Marc Grabanski
JavaScript Jabber 177 JSJ UI Validation with Oren Rubin
JavaScript Jabber 175 JSJ Elm with Evan Czaplicki and Richard Feldman
JavaScript Jabber JSJ 469: The Case for JavaScript Iterators and Generators, part 2
JavaScript Jabber 174 JSJ npm 3 with Rebecca Turner and Forrest Norvell
JavaScript Jabber 188 JSJ JavaScript Code Smells with Elijah Manor
JavaScript Jabber 232 JSJ GunDB and Databases with Mark Nadal
JavaScript Jabber 172 JSJ NodeSchool with Jason Rhodes
JavaScript Jabber High-Performance Networking: Key Resources and Tools for Web Developers - JSJ 637
JavaScript Jabber 168 JSJ The Future of JavaScript with Jafar Husain
JavaScript Jabber JSJ 268 Building Microsoft Office Extensions with JavaScript with Tristan Davis and Sean Laberee
JavaScript Jabber JSJ 306: The Framework Summit with Joe Eames
JavaScript Jabber 167 JSJ TypeScript and Angular with Jonathan Turner and Alex Eagle
JavaScript Jabber 014 JSJ SVG and Data Visualization with Chris Bannon
JavaScript Jabber TC39 and Upcoming Proposals for ECMAScript (PART 1) - JSJ 532
JavaScript Jabber JSJ 477: Understanding Search Engines and SEO (for devs) - Part 2
JavaScript Jabber 166 JSJ New Relic with Wraithan and Ben Weintraub
JavaScript Jabber JSJ 316: Visual Studio Code with Rachel MacFarlane and Matt Bierner LIVE at Microsoft Build
JavaScript Jabber 038 JSJ Jasmine with Justin Searls
JavaScript Jabber BONUS: Relationships Matter Most
JavaScript Jabber 047 JSJ Specialized vs Monolithic with James Halliday and Tom Dale
JavaScript Jabber 042 JSJ CSS and CSS Superset Languages
JavaScript Jabber 184 JSJ Web Performance with Nik Molnar
JavaScript Jabber 163 JSJ Flow with Jeff Morrison and Avik Chaudhuri
JavaScript Jabber 176 JSJ RethinkDB with Slava Akhmechet
JavaScript Jabber 153 JSJ Careers for Junior Developers with Aimee Knight
JavaScript Jabber JSJ 322: Building SharePoint Extensions with JavaScript with Vesa Juvonen LIVE at Microsoft Build
JavaScript Jabber 157 Moving Your Rendering Engine to React with Amit Kaufman and Avi Marcus
JavaScript Jabber 154 JSJ Raygun.io Error Reporting and Workflow with John-Daniel Trask
JavaScript Jabber JSJ 427: How to Start a Side Hustle as a Programmer with Mani Vaya
JavaScript Jabber 152 JSJ GraphQL and Relay with Nick Schrock and Joe Savona
JavaScript Jabber MeteorJS ft. Filipe Névola - JSJ 506
JavaScript Jabber 150 JSJ OIMs with Richard Kennard, Geraint Luff, and David Luecke
JavaScript Jabber How to Check Your Application Security featuring Liran Tal - JSJ 493
JavaScript Jabber 148 JSJ i.cx and EveryBit.js with Matt Asher and Dann Toliver
JavaScript Jabber JSJ 386: Gatsby.js with Chris Biscardi
JavaScript Jabber WebAuthn With Dan Moore - JSJ 562
JavaScript Jabber JSJ 327: "Greenlock and LetsEncrypt" with AJ O'Neal
JavaScript Jabber JSJ 406: Security in Node
JavaScript Jabber What's New with Elm? ft. Lindsay Wardell - JSJ 527
JavaScript Jabber 147 JSJ io.js with Isaac Schleuter and Mikeal Rogers
JavaScript Jabber Where is JAMstack and Dev Tooling Headed Today? - Putting JetPacks on Developers ft. Tejas Kumar - JSJ 514
JavaScript Jabber 146 JSJ React with Christopher Chedeau and Jordan Walke
JavaScript Jabber BONUS: Measuring Apps and Entrepreneurship with John-Daniel Trask
JavaScript Jabber JSJ 462: The Ultimate Guide to JavaScript Testing with Lucas da Costa
JavaScript Jabber Wix Velo with Yoav Abrahami - JSJ 558
JavaScript Jabber 144 JSJ Marionette.js 2.0 with Sam Saccone
JavaScript Jabber JSJ 340: JavaScript Docker with Julian Fahrer
JavaScript Jabber 143 JSJ Teaching Programming and Computer Science with Pamela Fox
JavaScript Jabber 141 JSJ Firefox OS with Jason Weathersby
JavaScript Jabber JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna Henningsen
JavaScript Jabber 140 JSJ Using Art to Get and Keep People Interested in Programming with Jenn Schiffer
JavaScript Jabber JSJ 350: JavaScript Jabber Celebrates Episode 350!
JavaScript Jabber 139 JSJ The Mozilla Developer Network with Les Orchard and David Walsh
JavaScript Jabber Episode 500 Celebration! - JSJ 500
JavaScript Jabber JSJ 352: Caffeinated Style Sheets: Supporting High Level CSS with JavaScript with Tommy Hodgins
JavaScript Jabber 106 JSJ Protractor with Julie Ralph
JavaScript Jabber 138 JSJ {Track:js} with Todd Gardner
JavaScript Jabber 135 JSJ Smallest Federated Wiki with Ward Cunningham
JavaScript Jabber Navigating Online Events and Conferences - JSJ 541
JavaScript Jabber 127 JSJ Changes in npm-Land with Forrest Norvell, Rebecca Turner, Ben Coe, and Isaac Z. Schlueter
JavaScript Jabber 126 JSJ The Ionic Framework with Max Lynch and Tyler Renelle
JavaScript Jabber 124 JSJ The Origin of Javascript with Brendan Eich
JavaScript Jabber 133 JSJ Remote Work with Mike Hostetler
JavaScript Jabber Supply Chain Security - Part 2 - JSJ 525
JavaScript Jabber 123 JSJ Traceur with Erik Arvidsson
JavaScript Jabber JSJ 380: Expo for Web with Charlie Cheever
JavaScript Jabber Personal Branding for Developers with Morad Stern - JSJ 642
JavaScript Jabber JSJ 253 Gomix with Daniel X Moore
JavaScript Jabber 120 JSJ Google Polymer with Rob Dodson and Eric Bidelman
JavaScript Jabber Unveiling Qwik and JavaScript Streamlining Web Development with Shai Reznik - JSJ 628
JavaScript Jabber 069 JSJ The Application Cache with Jake Archibald
JavaScript Jabber JSJ 276: Vue.js with Maximilian Schwarzmüller
JavaScript Jabber 115 JSJ The ES6 Module Loader Polyfill, SystemJS, and jspm with Guy Bedford
JavaScript Jabber Supply Chain Security - Part 1 - JSJ 524
JavaScript Jabber 110 JSJ Zones with Brian Ford
JavaScript Jabber 104 JSJ Hypermedia APIs with Steve Klabnik
JavaScript Jabber 103 JSJ Robots with Raquel Vélez
JavaScript Jabber JSJ 376: Trix: A Rich Text Editor for Everyday Writing with Javan Makhmali
JavaScript Jabber 136 JSJ TrackingJS with Eduardo Lundgren
JavaScript Jabber 116 JSJ jQuery UI vs KendoUI with Burke Holland and TJ VanToll
JavaScript Jabber 052 JSJ Node & NPM with Isaac Schlueter
JavaScript Jabber 099 JSJ npm, Inc. with Isaac Schlueter, Laurie Voss, and Rod Boothby
JavaScript Jabber 098 JSJ Assemble.io with Brian Woodward and Jon Schlinkert
JavaScript Jabber 097 JSJ Gulp.js with Eric Schoffstall
JavaScript Jabber 095 JSJ AngularUI with Dean Sofer
JavaScript Jabber 118 JSJ Web Developer Skills
JavaScript Jabber 093 JSJ The New York Times and JavaScript with Eitan Konigsburg, Alastair Coote and Reed Emmons
JavaScript Jabber 091 JSJ JSON APIs
JavaScript Jabber 090 JSJ Users Groups
JavaScript Jabber JSJ 382: Mental Health with Anatoliy Zaslavskiy
JavaScript Jabber Changes in the JAMstack Landscape with Sean C Davis - JSJ 482
JavaScript Jabber 088 JSJ Lazy.js with Daniel Tao
JavaScript Jabber 087 JSJ TC39 with Alex Russell
JavaScript Jabber 030 JSJ Learning & Teaching JavaScript with Noel Rappin
JavaScript Jabber Structuring Node.js Applications: Event Loop, Metrics, and Efficient Processing Techniques - JSJ 657
JavaScript Jabber The Story of Mel with Tomer Lichtash and David Frankiel - JSJ 544
JavaScript Jabber Upcoming Performance Metrics for the Web - JSJ 542
JavaScript Jabber 083 JSJ FRP and RxJS with Matthew Podwysocki
JavaScript Jabber 081 JSJ Promises for Testing Async JavaScript with Pete Hodgson
JavaScript Jabber JSJ 354: Elm with Richard Feldman
JavaScript Jabber 077 JSJ Monocle with Alex MacCaw
JavaScript Jabber JSJ 447: Using Javascript for Data Analysis and Data Science with Daniel Lathrop
JavaScript Jabber BONUS: Adding a Content Engine to Your App with a Headless CMS with Jake Lumetta
JavaScript Jabber 075 JSJ Maintainable JavaScript with Nicholas Zakas
JavaScript Jabber 016 JSJ SQL and NoSQL
JavaScript Jabber 071 JSJ JavaScript Strategies at Microsoft with Scott Hanselman
JavaScript Jabber Interactive Coding Tutorials with Tomek Salkowski: Enhancing Developer Experiences - JSJ 651
JavaScript Jabber JSJ 287: Blockchain and JS with Ari Lerner
JavaScript Jabber 068 JSJ ES6 with Aaron Frost
JavaScript Jabber 001 JSJ Asynchronous Programming
JavaScript Jabber Slaughtering Sacred Cows: Reconsidering Software Dev Truisms - JSJ 653
JavaScript Jabber 063 JSJ Burnout
JavaScript Jabber 062 JSJ Dojo with Dylan Schiemann
JavaScript Jabber 149 JSJ Passenger Enterprise with Node.js with Hongli Lai and Tinco Andringa
JavaScript Jabber What Is Functional Programming and What It's Not With Lane Wagner- JSJ 557
JavaScript Jabber 060 JSJ Development Environments
JavaScript Jabber Using Storybook and Nuxt To Quickly Build Websites - JSJ 531
JavaScript Jabber 059 JSJ jQuery Mobile with Todd Parker
JavaScript Jabber 057 JSJ Functional Programming with Zach Kessin
JavaScript Jabber 056 JSJ Marionette.js with Derick Bailey
JavaScript Jabber 082 JSJ JSHint with Anton Kovalyov
JavaScript Jabber Builder.io and Qwik - JSJ 540
JavaScript Jabber JSJ 458: Codota Tabnine and the Rise of Ai-powered Developer Tooling with Kyle Simpson
JavaScript Jabber How to Get Hired at a FANG Company - BONUS
JavaScript Jabber Opinionated Core Web Vitals - JSJ 647
JavaScript Jabber 055 JSJ Web Developer Skills
JavaScript Jabber Deep Dive into Metrics and Monitoring with Prometheus and Grafana - JSJ 645
JavaScript Jabber Monitoring Performance and Core Web Vitals ft. Bianca Grizhar and Sumitra Manga - JSJ 501
JavaScript Jabber 053 JSJ Software Team Dynamics
JavaScript Jabber Flutter Essentials ft. Allen Wyma - JSJ 494
JavaScript Jabber 145 JSJ Meteor.js with Matt DeBergalis
JavaScript Jabber Adapting to Effect Cluster: JavaScript Developers' Guide to Enhancing Code Maintainability - JSJ 639
JavaScript Jabber 051 JSJ Finding a Job
JavaScript Jabber 049 JSJ MooTools with Valerio Proietti and Arian Stolwijk
JavaScript Jabber 044 JSJ Book Club: Effective JavaScript with David Herman
JavaScript Jabber Framework Comparisons, Real User Metrics, and Effective Performance Tools - JSJ 640
JavaScript Jabber State Management ft. Assaf Krintza - JSJ 508
JavaScript Jabber 040 JSJ Conferences
JavaScript Jabber 039 JSJ Sweet.js with Tim Disney
JavaScript Jabber JSJ 360: Evolutionary Design with James Shore
JavaScript Jabber JSJ 264 Mendel with Irae Carvalho
JavaScript Jabber 037 JSJ Promises with Domenic Denicola and Kris Kowal
JavaScript Jabber 015 JSJ Open Discussion
JavaScript Jabber 013 JSJ Knockout.js with Steven Sanderson
JavaScript Jabber 067 JSJ Testem with Toby Ho
JavaScript Jabber 035 JSJ node-webkit
JavaScript Jabber 033 JSJ enyo.js
JavaScript Jabber 032 JSJ Angular.js
JavaScript Jabber JSJ 262 Mozilla Firefox Developer Tools with Jason Laster
JavaScript Jabber Crafting Code and Community: AI, LeetCode, and Meetups - JSJ 644
JavaScript Jabber JSJ 365: Do You Need a Front-End Framework?
JavaScript Jabber 029 JSJ Bower.js with Alex MacCaw and Jacob Thornton
JavaScript Jabber 028 JSJ Greenfield vs Brownfield Projects
JavaScript Jabber 027 JSJ The JavaScript Community
JavaScript Jabber How to Become a Senior Developer with Shem Magnezi - JSJ 521
JavaScript Jabber Web3 with Nik Kalyani - JSJ 520
JavaScript Jabber 023 JSJ Phantom.js with Ariya Hidayat
JavaScript Jabber 022 JSJ Node.js on Azure with Glenn Block
JavaScript Jabber 096 JSJ The Challenges of Large Single Page JavaScript Applications with Bart Wood
JavaScript Jabber 017 JSJ CoffeeScript with Jeremy Ashkenas
JavaScript Jabber 011 JSJ Can HTML5 and JavaScript Really Replace Flash?
JavaScript Jabber JSJ 426: Killing the Release Night with Progressive Delivery with Dave Karow
JavaScript Jabber 009 JSJ Testing JavaScript with Joe Eames
JavaScript Jabber HTMX and InterCooler ft. Carson Gross - JSJ 513
JavaScript Jabber Transforming React Development: The Experimental Compiler’s Approach to Memoization and Performance - JSJ 636
JavaScript Jabber Catching Up on InertiaJS with Jonathan Reinink - JSJ 511
JavaScript Jabber Software Development as a Craft with Netta Bondy - JSJ 551
JavaScript Jabber 008 JSJ V8 and Dart with Lars Bak and Kasper Lund
JavaScript Jabber Core Web Vitals and Whatnot - JSJ 537
JavaScript Jabber D3 and Data Visualization ft. Ian Johnson - JSJ 507
JavaScript Jabber JSJ 337: Microstates.js – Composable State Primitives for JavaScript with Charles Lowell & Taras Mankovski
JavaScript Jabber Creeds of Craftsmanship - JSJ 505
JavaScript Jabber JSJ 404: Edge on Chromium with Chris Heilmann
JavaScript Jabber Navigating Web Development Challenges - JSJ 624
JavaScript Jabber JSJ 411: Unit Testing Jest with Daniel Caldas
JavaScript Jabber 3 Fundamental Pillars You Need to Succeed as an Entrepreneur - BONUS
JavaScript Jabber Javascript and the Blockchain with Max Kordek - JSJ 503
JavaScript Jabber Alpinejs, Microservices, Code Completion, and Getting Paid for Open Source with Caleb Porzio - JSJ 497
JavaScript Jabber Opinionated Core Web Vitals - JSJ 495
JavaScript Jabber Virtual DOM and the React Way, Part 1 - JSJ 512
JavaScript Jabber The New JAMstack with Brian Rinaldi - JSJ 491
JavaScript Jabber Web Performance and the Google WordPress Team with Felix Arntz - JSJ 548
JavaScript Jabber The React Way & Opinionated Practices with Ian Schwartz - JSJ 488
JavaScript Jabber CrUX and Core Web Vitals - What to Measure on the Web with Rick Viscomi - JSJ 486
JavaScript Jabber JSJ 440: Why Serverless with Gareth McCumskey
JavaScript Jabber 054 JSJ JavaScript Parsing, ASTs, and Language Grammar w/ David Herman and Ariya Hidayat
JavaScript Jabber Gal Schlezinger and Edge Functions - JSJ 536
JavaScript Jabber JSJ 408: Reading Source Code with Carl Mungazi
JavaScript Jabber 162 JSJ ESLint with Jamund Ferguson
JavaScript Jabber 187 JSJ Vue.js with Evan You
JavaScript Jabber 156 JSJ Soft Skills and Marketing Yourself as a Software Developer with John Sonmez
JavaScript Jabber SEO for Developers ft. Mordy Oberstein - JSJ 509
JavaScript Jabber 058 JSJ Building Accessible Websites with Brian Hogan
JavaScript Jabber JSJ 247 Building a Development Environment with Cory House
JavaScript Jabber 085 JSJ Huxley with Pete Hunt
JavaScript Jabber 078 Working From Home
JavaScript Jabber 050 JSJ QUnit with Jörn Zaefferer
JavaScript Jabber JSJ 423: State of JS
JavaScript Jabber 130 JSJ Browser Tools and Extensions
JavaScript Jabber Find Out More About Elliot Johnson - BONUS
JavaScript Jabber JSJ 418: Security Scary Stories and How to Avoid Them with Kevin A McGrail
JavaScript Jabber Getting to Know Bruce A. Tate - BONUS
JavaScript Jabber Everything Remult with Noam Honig and Yoni Rapoport - JSJ 579
JavaScript Jabber Jason Weimann - Learn Video Game Development with Chuck - BONUS
JavaScript Jabber TanStack Router with Tanner Linsley - JSJ 578
JavaScript Jabber How Do You Stop Hating Your Job? - BONUS
JavaScript Jabber Reverse Engineering with Joyce Lin - JSJ 577
JavaScript Jabber JSJ 480: Are Micro Frontends worth the effort? (And if so when?)
JavaScript Jabber BONUS: How Opportunities Come Your Way When You're an Influencer
JavaScript Jabber Signals: What You Should Know with Tejas Kumar - JSJ 576
JavaScript Jabber The Best of JavaScript and Ruby in 2023 - JSJ 575
JavaScript Jabber JSJ 479: Practical Microservices with Ethan Garofolo
JavaScript Jabber JSJ 299: How To Learn JavaScript When You're Not a Developer with Chris Ferdinandi
JavaScript Jabber BONUS: What is Charles Max Wood's Biggest Payoff for Being a Dev Influencer?
JavaScript Jabber Functional Programming with Ian Schwartz - JSJ 574
JavaScript Jabber What To Expect For JSNation - BONUS
JavaScript Jabber Introducing Codux With Nadav Abrahami & Tom Raviv - JSJ 573
JavaScript Jabber Build Your Game Using JavaScript with Andrzej Mazur- JSJ 572
JavaScript Jabber JSJ 392: The Murky Past and Misty Future of JavaScript with Douglas Crockford
JavaScript Jabber The State of JS Frameworks with Ryan Carniato: Part 2 - JSJ 571
JavaScript Jabber 114 JSJ Asynchronous UI and Non-Blocking Interactions with Elliott Kember
JavaScript Jabber 117 JSJ The Koa Framework with Gerred Dillon and Will Conant
JavaScript Jabber The State of JS Frameworks with Ryan Carniato: Part 1 - JSJ 570
JavaScript Jabber Web Performance With Alex Russell - JSJ 569
JavaScript Jabber 113 JSJ Community Dynamics with Reginald Braithwaite
JavaScript Jabber React Native & Every-Platform Embeddable UI With Taz Singh - JSJ 568
JavaScript Jabber BONUS: How Jason Weimann Became a Game Developer
JavaScript Jabber JSJ 452: Caddy 2 Web Server with Matthew Holt
JavaScript Jabber JSJ 475: DevOps for the JavaScript Developer
JavaScript Jabber JSJ 473: The Elements framework with Chris Mather
JavaScript Jabber Providing The Best User Experiences on the Web With Vercel- BONUS
JavaScript Jabber Front-End Hydration - JSJ 567
JavaScript Jabber JSJ 472: RedwoodJS Brings Full-Stack to the JAMstack with Anthony Campolo
JavaScript Jabber 002 JSJ The Right Way to Build Web Applications
JavaScript Jabber Marvels Of Using Svelte and SvelteKit - JSJ 566
JavaScript Jabber JSJ 470: Fine Tuning Your Psychological Stack, or DevOps For Your Brain
JavaScript Jabber Runtime Security With Gal Weizman - JSJ 565
JavaScript Jabber JSJ 468: The case for JavaScript iterators, part 1
JavaScript Jabber JSJ 460: The Things Every JavaScript Developer Must Know, Part 2
JavaScript Jabber JSJ 454: Mongoose, Mongo and Object Document Mapping (ODM) with Valeri Karpov
JavaScript Jabber 180 JSJ Finding a Job
JavaScript Jabber How To Plan For Success In 2023 - JSJ 564
JavaScript Jabber Qwik Part II With Misko Hevery - JSJ 563
JavaScript Jabber BONUS: How to do LARGE Volumes of HIGH Quality Work - While Spending Fewer Hours Working
JavaScript Jabber JSJ 459: Codota Tabnine and the Rise of Ai-powered Developer Tooling with Kyle Simpson PT 2
JavaScript Jabber 213 JSJ Developer Evangelism with Greg Baugues
JavaScript Jabber Blockchain with Max Kordek - JSJ 529
JavaScript Jabber JSJ 399: Debugging with Async/Await with Valeri Karpov
JavaScript Jabber JSJ 457: Career Transitioning with Laura Harvey
JavaScript Jabber JSJ 456: Developer-First Security and Security Tooling For Developers with Liran Tal & Brian Vermeer
JavaScript Jabber JSJ 455: Introducing and Understanding Svelte and Sapper with Mark Volkmann
JavaScript Jabber JSJ 453: Debugging Third Party JavaScript with Ben Vinegar
JavaScript Jabber JSJ 446: Achieving Work-Life Balance, Especially When WFH
JavaScript Jabber Exploring Local-First Applications and Data Synchronization Challenges - JSJ 654
JavaScript Jabber JSJ 445: Augmented Reality for Mobile Browsers with Connell Gauld
JavaScript Jabber JSJ 441: The Present and Future of JavaScript Bundling and Delivery with Yoav Weiss
JavaScript Jabber 236 JSJ Interview with Mads Kristensen from Microsoft Ignite
JavaScript Jabber JSJ 439: More Jabber About Less JavaScript with Alex Russell
JavaScript Jabber Remix and EpicWeb.dev with Kent C. Dodds - JSJ 554
JavaScript Jabber Unpacking Deno 2: Code Stability, Free Speech, and more - JSJ 648
JavaScript Jabber 019 JSJ Browserify with James Halliday
JavaScript Jabber JSJ 419: Google App Script with Ben Collins
JavaScript Jabber 034 JSJ Ember.js
JavaScript Jabber JSJ 465:The Power of Micro Front-Ends with Michael Geers
JavaScript Jabber JSJ 395: The New Ember with Mike North
JavaScript Jabber The Alphabet Soup of Performance Measurements - JSJ 622
JavaScript Jabber 031 JSJ history.js
JavaScript Jabber JSJ 436: MongoDB Basics with Joe Karlsson
JavaScript Jabber JSJ 379: FindCollabs and Podcasting with Jeff Meyerson
JavaScript Jabber JSJ 433: Understanding the Browser Layer with Noam Rosenthal
JavaScript Jabber New Frontiers in Web Platform Development with Bruce Lawson - JSJ 634
JavaScript Jabber Pain-Free Automated Deployments with DigitalOcean's App Platform - BONUS
JavaScript Jabber 061 JSJ Functional Reactive Programming with Juha Paananen and Joe Fiorini
JavaScript Jabber JSJ 424: UI5 and web components with Peter Muessig
JavaScript Jabber 010 JSJ Node.js
JavaScript Jabber JSJ 422: CSS and Houdini with Una Kravets
JavaScript Jabber JSJ 421: Semantic HTML with Bruce Lawson
JavaScript Jabber BONUS: Continuing Your Learning Journey by Finding Mentors as an Influencer
JavaScript Jabber JSJ 420: OpenAPI, Redoc, and API Documentation with Adam Altman
JavaScript Jabber JSJ 417: Serverless with Microsoft Azure with Burke Holland
JavaScript Jabber TypeScript, ESLint, and TypeScript ESLint with Josh Goldberg - JSJ 605
JavaScript Jabber Harnessing Module Federation and Micro Front-Ends in JavaScript Development - JSJ 603
JavaScript Jabber Unpacking Core Web Vitals - JSJ 620
JavaScript Jabber 072 JSJ Screencasts
JavaScript Jabber JSJ 416: GraphQL Developer Tools with Sean Grove
JavaScript Jabber JSJ 414: JavaScript Jabber Still at RxJs Live
JavaScript Jabber JSJ 409: Swagger and Open API with Josh Ponelat
JavaScript Jabber JSJ 405: Machine Learning with Gant Laborde
JavaScript Jabber JSJ 407: Reactive JavaScript and Storybook with Dean Radcliffe
JavaScript Jabber JSJ 450: Native Features Inside The Browser - Introducing Google's Project Fugu with Thomas Steiner
JavaScript Jabber JSJ 464: Web Components FTW with Ben Farrell
JavaScript Jabber JSJ 400: The Influence of JavaScript Jabber
JavaScript Jabber 185 JSJ PouchDB with Nolan Lawson
JavaScript Jabber DevOps for JavaScript ft. Will Button - JSJ 502
JavaScript Jabber 020 JSJ Cloud9
JavaScript Jabber 076 JSJ Meteor.js with Marcus Phillips and Fred Zirdung
JavaScript Jabber Astro with Fred K. Schott - JSJ 561
JavaScript Jabber JSJ 398: Node 12 with Paige Niedringhaus
JavaScript Jabber JSJ 396: Publishing Your Book with Jonathan Lee Martin
JavaScript Jabber JSJ 342: Aurelia in Action with Sean Hunter
JavaScript Jabber JSJ 394: SMS Integration with Dominik Kundel
JavaScript Jabber JSJ 393: Why You Should Be Using Web Workers with Surma
JavaScript Jabber JSJ 336: “The Origin of ESLint” with Nicholas Zakas
JavaScript Jabber JSJ 332: “You Learned JavaScript, Now What?” with Chris Heilmann
JavaScript Jabber JSJ 391: Debugging with Todd Gardner
JavaScript Jabber JSJ 330: “AWS: Amplify” with Nader Dabit
JavaScript Jabber JSJ 448: MongoDB Schema Fundamentals with Joe Karlsson
JavaScript Jabber JSJ 323: "Building a JavaScript platform that gives you the power to build your own CDN" with Kurt Mackey
JavaScript Jabber Things JavaScript Developers Should Know, Part 2 - JSJ 485
JavaScript Jabber JSJ 383: What is JavaScript?
JavaScript Jabber Transitioning a Large Front-End Codebase to TypeScript ft. Priscila Oliveira and Mark Story – JSJ 498
JavaScript Jabber The 3 Essentials for Successful Job Outcomes - BONUS
JavaScript Jabber JSJ 378: Stencil and Design Systems with Josh Thomas and Mike Hartington
JavaScript Jabber JSJ 372: Kubernetes Docker and Devops with Jessica Deen LIVE from Microsoft BUILD
JavaScript Jabber React Component and State Management - JSJ 526
JavaScript Jabber JSJ 474: Things JavaScript Developers Should Know, Part 1
JavaScript Jabber JSJ 371: The Benefits and Challenges of Server-Side Rendering (SSR) with Dan Shappir
JavaScript Jabber BONUS: How to Speed Up Your Website For Fun and Profit with Inian Parameshwaran
JavaScript Jabber JSJ 370: Azure Functions Part II with Jeff Hollan LIVE at Microsoft BUILD
JavaScript Jabber JSJ 368: TypeScript - Good or Bad
JavaScript Jabber JSJ 390: Transposit with Adam Leventhal
JavaScript Jabber JSJ 369: Azure Functions with Colby Tresness LIVE at MIcrosoft BUILD
JavaScript Jabber JSJ 367: Pair Programming
JavaScript Jabber AgGrid: From Open Source to Successful Business ft. Niall Crosby - JSJ 504
JavaScript Jabber Node in the Browser and Much more: Web Containers with Eric Simons - JSJ 487
JavaScript Jabber JSJ 463: Building Web Applications with Firebase
JavaScript Jabber JSJ 366: npm with Mikeal Rogers
JavaScript Jabber JSJ 364: Ember Octane with Sam Selikoff
JavaScript Jabber 238 JSJ Intellectual Property and Software Forensics with Bob Zeidman
JavaScript Jabber BONUS: How to do LARGE Volumes of HIGH Quality Work - While Spending Fewer Hours Working
JavaScript Jabber JSJ 362: Accessibility with Chris DeMars
JavaScript Jabber JSJ 363: Practical JAMstack and Serverless with Gareth McCumskey
JavaScript Jabber JSJ 361: Enough with the JS Already with Nicholas Zakas
JavaScript Jabber Virtual DOM and the React Way, Part Deux - JSJ 518
JavaScript Jabber How to Stay Current with JavaScript - JSJ 499
JavaScript Jabber NoSQL and RavenDB - JSJ 530
JavaScript Jabber JSJ 357: Event-Stream & Package Vulnerabilities with Richard Feldman and Hillel Wayne
JavaScript Jabber JSJ 356: Build Websites Like It's 2005 with Keith Cirkel
JavaScript Jabber 233 JSJ Google Chrome Extensions with John Sonmez
JavaScript Jabber JSJ 353: Signal R with Brady Gaster LIVE at Microsoft Ignite
JavaScript Jabber JSJ 347: JAMstack with Divya Sasidharan & Phil Hawksworth
JavaScript Jabber JSJ 351: Dinero.js with Sarah Dayan
JavaScript Jabber JSJ 344: Inclusive Components with Heydon Pickering
JavaScript Jabber JSJ 341: Testing in JavaScript with Gil Tayar
JavaScript Jabber JSJ 335: “CanJS 4.0” with Justin Meyer
JavaScript Jabber JSJ 333: “JavaScript 2018: Things You Need to Know, and a Few You Can Skip” with Ethan Brown
JavaScript Jabber JSJ 444: Coding Front-end JavaScript for Accessibility with Neha Sharma
JavaScript Jabber 231 JSJ Codewars with Nathan Doctor, Jake Hoffner, and Dan Nolan
JavaScript Jabber JSJ 410: Iterating on Open Source
JavaScript Jabber JSJ 415: Progressive Web Apps with Maximiliano Firtman
JavaScript Jabber JSJ 412: Svelte and Sapper with Svelte Master
JavaScript Jabber JSJ 403: Why Developers Need Social Skills with Mani Vaya
JavaScript Jabber JSJ 387: How to Stay Current in the Tech Field
JavaScript Jabber JSJ 385: What Can You Build with JavaScript?
JavaScript Jabber JSJ 381: Building a Personal Brand with John Sonmez
JavaScript Jabber JSJ 377: Bringing Maps and Location Into Your Apps with the ArcGIS API for JavaScript with Rene Rubalcava
JavaScript Jabber 221 JSJ Visual Studio Code with Wade Anderson Live From Microsoft Build 2016
JavaScript Jabber JSJ 375: Are You Hurting the Web?
JavaScript Jabber JSJ 373: What Do You Need to Do to Get a Website Up?
JavaScript Jabber 218 JSJ Ember.js with Yehuda Katz
JavaScript Jabber JSJ 359: Productivity with Mani Vaya
JavaScript Jabber JSJ 355: Progressive Web Apps with Aaron Gustafson LIVE at Microsoft Ignite
JavaScript Jabber JSJ 346: Azure Pipelines with Ed Thomson LIVE at Microsoft Ignite
JavaScript Jabber JSJ 317: Prisma with Johannes Schickling
JavaScript Jabber JSJ 315: The effects of JS on CSS with Greg Whitworth
JavaScript Jabber JSJ 313: Light Functional JavaScript with Kyle Simpson
JavaScript Jabber JSJ 300: Celebration
JavaScript Jabber JSJ 291: Serverless For JavaScript with Gareth McCumskey
JavaScript Jabber JSJ 295: Developers as Entrepreneurs with Ryan Glover
JavaScript Jabber JSJ 293: Big Data with Nishant Thacker
JavaScript Jabber JSJ 292: CosmosDB with Kirill Gavrylyuk
JavaScript Jabber JSJ 285 : Finding a Job Even If You're Not a Senior Developer by Charles Max Wood
JavaScript Jabber JSJ 284 : Helping Developers Build Healthy Bodies
JavaScript Jabber JSJ 277: Dojo 2 with Dylan Schiemann and Kitson Kelly
JavaScript Jabber JSJ 309: WebAssembly and JavaScript with Ben Titzer
JavaScript Jabber 048 JSJ Why JavaScript Is Hard

JavaScript Jabber

Subscribe

Follow

122 JSJ Socket.IO with Guillermo Rauch

Show Notes

Transcript