Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Sync – Realtime partials with Rails

chrismccord.com

Post reply on HN
Print view View original

11–20 of 30 posts

Re: Show HN: Sync – Realtime partials with Rails

#11

Post by chrismccord »

hemancuso wrote: post #10

Looks neat, but I am curious why you would pick such an overused name for the project. Perhaps call it PartialSync, or something you could google?

I struggled with the naming to be honest, but settled on something short and sweet that sounded nice to me. Googling hopefully won't be a problem when coupled with a copule modifiers, ie "sync realtime partials"

Re: Show HN: Sync – Realtime partials with Rails

#14

Post by chrismccord »

benradler wrote: post #12

Me gusta. Can this potentially replace a client-side MVC framework like backbone.js or ember.js entirely or are there limitations?

Sync is an alternative to Ember/Backbone, but not a replacement. If you're trying to replicate desktop software in the browser for instance, a heavy client-side framework is the way to go; however, for certain use cases for web applications with lots of "richness" but not trying to replicate desktop level interactivity, think Basecamp, Reddit, Facebook, Twitter, the Sync approach could definitely hold its own against these types of apps. I've greatly enjoyed building Backbone apps, and I look forward to playing with Ember, but not every web application needs to be rendered client-side against a JSON api. Sync also allows you to wire up your own javascript, so you could even use backbone models submitting over JSON and render your realtime views with Sync on the server. I'm excited to see how far we can take this approach.

Re: Show HN: Sync – Realtime partials with Rails

#16

Post by benradler »

chrismccord wrote: post #14
benradler wrote: post #12

Me gusta. Can this potentially replace a client-side MVC framework like backbone.js or ember.js entirely or are there limitations?

Sync is an alternative to Ember/Backbone, but not a replacement. If you're trying to replicate desktop software in the browser for instance, a heavy client-side framework is the way to go; however, for certain use cases for web applications with lots of "richness" but not trying to replicate desktop level interactivity, think Basecamp, Reddit, Facebook, Twitter, the Sync approach could definitely hold its own against…

thanks for the info chris, I will be following the project closely. I think I will try and implement it in one of my instagram-API driven web apps as a test.

Re: Show HN: Sync – Realtime partials with Rails

#17

Post by chrismccord »

benradler wrote: post #16
chrismccord wrote: post #14

Earlier quoted context omitted.

Sync is an alternative to Ember/Backbone, but not a replacement. If you're trying to replicate desktop software in the browser for instance, a heavy client-side framework is the way to go; however, for certain use cases for web applications with lots of "richness" but not trying to replicate desktop level interactivity, think Basecamp, Reddit, Facebook, Twitter, the Sync approach could definitely hold its own against…

thanks for the info chris, I will be following the project closely. I think I will try and implement it in one of my instagram-API driven web apps as a test.

No problem. Let me know how it goes

Re: Show HN: Sync – Realtime partials with Rails

#18

Post by scoot »

chrismccord wrote: post #9
tortilla wrote: post #8

Earlier quoted context omitted.

This looks perfect for a current project with a quite a bit of jQuery and partials. I may just redo using Sync. Do you have any recommendations for using on Heroku? Should I just use Pusher? Also does this work with Rails 4?

Faye will gladly run on Heroku with a foreman process, but I think Pusher is a tough choice to beat to get you up and running quickly. Sync does indeed support Rails 4. In fact, the demo app in the screencast is a Rails 4 app :)

So either Pusher or Faye are required, and Pusher is a commercial service, whilst Faye requires a dyno to run on Heroku? Have I got that right? TBH I'm not familiar with either Pusher or Faye, so just trying to grok the dependancies for Sync.

Re: Show HN: Sync – Realtime partials with Rails

#19

Post by chrismccord »

scoot wrote: post #18
chrismccord wrote: post #9

Earlier quoted context omitted.

Faye will gladly run on Heroku with a foreman process, but I think Pusher is a tough choice to beat to get you up and running quickly. Sync does indeed support Rails 4. In fact, the demo app in the screencast is a Rails 4 app :)

So either Pusher or Faye are required, and Pusher is a commercial service, whilst Faye requires a dyno to run on Heroku? Have I got that right? TBH I'm not familiar with either Pusher or Faye, so just trying to grok the dependancies for Sync.

That's correct. If on Heroku, Faye would run in it's own dyno process, while Pusher is a commercial product. Sync requires a pubsub server to talk to, so either is a must. I suggest prototyping out with the Pusher free plan if you just want to throw something up to experiment with.

Re: Show HN: Sync – Realtime partials with Rails

#20

Post by habosa »

Wow this really should become part of core Rails. This is definitely real time done the "rails way". I prefer Rails to anything else I've tried but my ideas increasingly revolve around real-time, so I either settle for a framework I like less or Rails + jQuery nonsense. This will be my new go to.
Post reply on HN