In the first article, we looked at the difference between Websockets and AJAX as transport mechanisms for data. In this article, I wanted to explore why single page apps fit in so well with the new realtime paradigm. What’s a Single Page App? In its most basic form a single page HTML5 app is a browser-based application that doesn’t do a full page refresh as the user interacts with the page.
Browser Wars: Websockets vs. AJAX. This is the first in a series of articles on Building Realtime HTML5 Apps.
I recently created a new framework called bone.io, and I wanted to share my thoughts and ideas on building realtime web applications. This series is going to be less of a how-to guide, and more of a 30,000 foot view of the realtime web and the potential for the next generation of web applications. A Brief History of Websockets Websockets is a new standard from 2011, that hopes to bring realtime (technically, “near-realtime”) communication to the web. Websockets provide full-duplex communication channels over a single TCP connection. As of this writing, every major browser supports Websockets, except for Android.
Unsuck your backbone. Grunt: The Node Developer's Sidekick. Backbone.js: Basics & Beyond.
Angular: The Component Orientedness It Makes Me Happy And Why. Being a geezer programmer ain’t all bad.
I’ve helped launch a west coast startup and created a data-driven internal application for a large company. I’ll cover reference materials I’ve used. Documentation lookup techniques that have served me well. Code snippets that Ember made it really easy to write. I will be answering questions afterward that match this regex /is ember (good|ready|hard|faster|stronger)/ with the response “Yes, shut up”. CinciJS - Lessons from Two Years of Backbone.js. CinciJS - AngularJS with Mike Ball.
Kanban Smackdown Part 2. Kanban Smackdown Part 1. Client-Side IDs with Ember Data. Why Client-Generated IDs?
In most client-side frameworks (e.g. Backbone, Angular, Ember) models created in the web browser get temporary IDs (client IDs) and get their permanent ID from the server after a successful save. For client-heavy applications, generating IDs on the client can simplify interaction with the server. Consider the case where the user creates a post with several attachments. You’ll need to make sure that the post is saved and has its ID resolved before attempting to save the child models in order to preserve this relationship. It can be liberating to know the ID of a model before it is saved. Because we’re using UUIDs, you could hypothetically find any record in your application given only an ID. If you find yourself generating secret IDs for resources (think account activation URLs) you may save yourself some code by using unique IDs.
About Us. AngularJS vs Ember - Evil Trout's Blog. Recently I got together with some local developers to discuss client side MVC frameworks.
There are so many factors to consider and so many options out there that selecting a framework can be overwhelming. To have an idea of all the possible alternatives have a look at TodoMVC. Backbonejs vs Angularjs : Demystifying the myths. I love the way how each and every discussion turns into the war of the frameworks. I have worked with BackboneJS and AngularJS quite extensively and have come across most of their short comings in production.