Preventing memory leaks in Backbone.js • Hacker News Board

Re: Preventing memory leaks in Backbone.js

#31

Post by throwa » Mon, Nov 12, 2012, 4:53 PM UTC

davidw wrote: post #27

atomical wrote: post #26

Earlier quoted context omitted.

Getting started with Ember is a lot harder than your comment admits. I tried Ember recently and there was still a lot of stuff that was broken including the data model. That would make building a non-trivial app hard.

What I'm investigating Backbone/Ember/whatever for is a semi-embedded device that will ship with a web interface, so some semblance of stability is a major plus.

As we speak it is used in production by many companies. Click this link to see them all:

https://github.com/emberjs/ember.js/wiki/Production-Deployme...

Shopitome is a very fresh deployment using emberjs based on this tweet sent today:

http://twitter.com/inkredabull/status/268017623428657153

http://www.shopittome.com/threads/signup

A few non trivial companies using emberjs in production are:

www.zendesk.com

http://www.squareup.com/

http://livingsocial.com/

http://www.groupon.com

http://www.desk.com/

http://basho.com/

http://travis-ci.org/

http://www.gooddata.com/

Re: Preventing memory leaks in Backbone.js

#32

Post by throwa » Mon, Nov 12, 2012, 4:58 PM UTC

atomical wrote: post #26

throwa wrote: post #17

Earlier quoted context omitted.

@davidw, Just use emberjs and focus on your app instead of boilerplate code. If you are coming from rails, emberjs is opinionated and should fit your style of thinking. Emberjs makes building non-trivial easy while backbone makes building non-trivial apps hard but makes building small simple app easy. People like talking about the size of emberjs but after you finishing stitching together numerous boilerplate code, y…

Getting started with Ember is a lot harder than your comment admits. I tried Ember recently and there was still a lot of stuff that was broken including the data model. That would make building a non-trivial app hard.

@atomical, the link to trek's article above puts it more succintly:

Ember applications start out with a complexity rating of 4/10 but never get much higher than 6/10, regardless of how sophisticated your application becomes. Backbone starts out at 1/10 but complexity grows linearly. This is a natural side effect of the types of applications the two frameworks were specifically created for.

Re: Preventing memory leaks in Backbone.js

#33

Post by davidw » Mon, Nov 12, 2012, 5:14 PM UTC

throwa wrote: post #31

davidw wrote: post #27

Earlier quoted context omitted.

What I'm investigating Backbone/Ember/whatever for is a semi-embedded device that will ship with a web interface, so some semblance of stability is a major plus.

As we speak it is used in production by many companies. Click this link to see them all: https://github.com/emberjs/ember.js/wiki/Production-Deployme... Shopitome is a very fresh deployment using emberjs based on this tweet sent today: http://twitter.com/inkredabull/status/268017623428657153 http://www.shopittome.com/threads/signup A few non trivial companies using emberjs in production are: www.zendesk.com http://ww…

Web production != shipping on devices production. You can very easily ship updates to the former whereas the latter is tricky. It means we need to be careful with everything we choose.

Re: Preventing memory leaks in Backbone.js

#34

Post by camus » Mon, Nov 12, 2012, 5:39 PM UTC

throwa wrote: post #17

davidw wrote: post #5

Ugh. Examples use Coffeescript instead of universally accessible Javascript. Looks very useful though; I've just started learning about Backbone, and the lack of a "right way of doing things" is disconcerting, coming from a lot of Rails usage lately. It takes me back to the days of doing a lot of stuff by hand. Even without that uncertainty, it's definitely a bit tricky to move to thinking about everything being in t…

@davidw, Just use emberjs and focus on your app instead of boilerplate code. If you are coming from rails, emberjs is opinionated and should fit your style of thinking. Emberjs makes building non-trivial easy while backbone makes building non-trivial apps hard but makes building small simple app easy. People like talking about the size of emberjs but after you finishing stitching together numerous boilerplate code, y…

Does Ember have a persistance layer ? like backbone sync ? anyway ,Ember is far from perfect too. The best javascript framework , though not free , is Ext JS.

Re: Preventing memory leaks in Backbone.js

#35

Post by throwa » Mon, Nov 12, 2012, 5:50 PM UTC

camus wrote: post #34

throwa wrote: post #17

Earlier quoted context omitted.

@davidw, Just use emberjs and focus on your app instead of boilerplate code. If you are coming from rails, emberjs is opinionated and should fit your style of thinking. Emberjs makes building non-trivial easy while backbone makes building non-trivial apps hard but makes building small simple app easy. People like talking about the size of emberjs but after you finishing stitching together numerous boilerplate code, y…

Does Ember have a persistance layer ? like backbone sync ? anyway ,Ember is far from perfect too. The best javascript framework , though not free , is Ext JS.

Yes it does. I have added enough links that touch on that.

https://github.com/emberjs/data

http://emberjs.com/guides/ember-data-lifecycle/

https://speakerdeck.com/tomdale/30 slides for the video below

http://www.youtube.com/watch?v=djhAsWGOImk Tom Dale - Ember-data

https://speakerdeck.com/tchak/ember-data

Re: Preventing memory leaks in Backbone.js

#36

Post by ldehaan » Tue, Nov 13, 2012, 4:24 AM UTC

I agree on the whole coffeescript thing, really it detracts from what you are trying to show. But on to the real point of commenting; I am implementing a system using backbone because it is a requirement of the company I am contracting for. I am writing several..plugins..I suppose you would call them, to make backbone work more like angular.js. If you're having issues with backbone and have a choice, I strongly recommend checking out angular. it is quite amazing and very flexible. while it seems like it should be opinionated it is actually quite flexible on what you must do once you learn how it works. A great example is view compositioning, it has a very strong templating system using definitions to create your own element sections. I am having a really hard time liking backbone, if I have to write all this code, really I would much rather write my own library to handle this stuff. So just my point of view along with a suggestion on something that I believe can take you much further and reduce the time you spend on the b.s.