Hey everyone! Backbone 1.0 has been released! I just happened to pop by their site and see that 1.0 is official, so I have no idea how long it has been out. Why didn’t anyone tell me?!?!? Anyway, there may be some of you out there wondering what this new version brings and how they can update their apps to bring in all the new awesomeness. Well, let’s take a gander at this new stuff. Continue reading →
This is hard for me to say because I know that there are a lot of people out there who have come to expect and enjoy the weekly posts on this site, but I have to leave the weekly post behind. Don’t worry, I’ll still post, but not very often. Continue reading →
I have exciting and potentially dreadful news. Currently this site is hosted on my previous employer’s servers. I’m currently taking steps to migrate this site to my own hosting. This is great news, except that it means that there is likely to be some down time. I’m not sure when exactly (some time over the weekend and maybe on Monday… maybe later, but not likely), but I will work my butt off to try to keep the site from being down too long. Sorry for the inconvenience, and thanks for your patience.
God bless you and happy coding!
It wasn’t long ago that I ran into a strange issue with Chrome. My Jasmine tests were failing because the timeout on the asynchronous actions was too short for Chrome, even though they worked perfectly fine for Firefox. This led to me writing some tests to see if Chrome’s WebSocket implementation was slow which gave some pretty interesting results. I’ve also heard some interesting results from my readers, so I decided to investigate some more. Continue reading →
In my last article where I talked about unit testing Socket.IO with Jasmine, there was a point where I mentioned that I needed to use timeouts that were a second and a half when doing the asynchronous connecting and disconnecting from the Socket.IO server. It was working just fine with 750 millisecond timeouts on Firefox, but when I tested it in Chrome, timeouts were being reached and the specs were failing. Let’s see if we can get to the bottom of this and figure out why Chrome failed so hard here. Continue reading →