Hacker News Reader

HenrikJoretegon Keeping It Realtime - conference for realtime tech

I'm one of the organizers, but yeah, we're a small dev shop in Eastern Washington who just love doing realtime stuff so we figured we'd try to throw a conference about it.

Didn't really realize how much interest there would be. Personally, I'm pretty pumped to hear about some of the new realtime frameworks. NullMQ, SocketStream, Derby, et. al.

Looking forward to adding some of those tools to the 'ol toolbelt.

HenrikJoretegon Re-using Backbone.js Models on the server with Node.js and Socket.io

Thank you. No offense taken :)

HenrikJoretegon Re-using Backbone.js Models on the server with Node.js and Socket.io

Thanks for that link. I hadn't seen that.

HenrikJoretegon Re-using Backbone.js Models on the server with Node.js and Socket.io

Thanks for your feedback. I've just been playing with this stuff and wanted to put it out there despite its warts.

Regarding the scaling issue. Yes. This is definitely a weakness (I actually mention it as a weakness in the last paragraph or so). We're working on a solution for that using redis as a sort of shared memory. But it's just not ready for primetime and I just figured I'd write up what I had going so far.

Regarding recursive updates of nested collections, the "mport" function in the post works well for re-inflating the entire state. But not quite as well for updates, but for this type of thing, I prefer piecemeal updates anyway, so we don't have to send as much data each time.

I'm definitely gonna check out dnode some more as well. Cheers.

HenrikJoretegon Building a single page app with Backbone.js, underscore.js and jQuery

True, what I'm talking about in my post is definitely a different paradigm than a more traditional web site where one of the goals is to make it widely accessible for any and all users/devices.

ps. thanks for reading my post simon, u da man!

HenrikJoretegon Building a single page app with Backbone.js, underscore.js and jQuery

Sammy.js does look quite cool. I've poked around the documentation, but haven't built anything with it yet.

I see what you're saying about "Javascript on Rails" but to me that's quite different than something like backbone. What you're talking about is more about "ajaxifying" a traditional browse-from-page-to-page experience. I definitely think there's value in that for improving the feel and responsiveness of a site. However, I'm more interested in truly emulating the desktop app experience where, once you log in there is no concept of browsing from page to page or "going back".

HenrikJoretegon Building a single page app with Backbone.js, underscore.js and jQuery

Thanks for your input. As you probably realized, my post was more about a strategy for apps that feel more like desktop apps, where once you're logged in, you're not really moving around from page to page at all. In my case it was a chat app where the whole app was useless without JS.

It's an interesting thought, though. However, I don't know if I'd see the need for something like backbone on any site where I was trying to support non-js browsers.

HenrikJoretegon Building a single page app with Backbone.js, underscore.js and jQuery

Jeremy, first of all. Thanks for Backbone! You guys rock.

I'm glad you liked my post.

Regarding "keeping models simple". Perhaps I wasn't so clear. My point here was mainly just that when I first started trying to build a model layer separate from the DOM (pre-backbone). I was very explicitly defining what attributes each model has and then also doing the corresponding DOM manipulations in my setters and getters. That got messy pretty quickly.

So, my point was not that you shouldn't add methods to your Backbone.Model's, but rather that you should keep view and controller logic out of your model layer.