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

Advice On & Instruction in The Use of Ember.js

trek.github.com

Post reply on HN
Print view View original

61–70 of 72 posts

Re: Advice On & Instruction in The Use of Ember.js

#61

Post by sirclueless »

eddieplan9 wrote: post #60
sirclueless wrote: post #54

Earlier quoted context omitted.

> What does double-loading mean? Basically, a web app that is usable (or at least readable) before all your JavaScript initialization is done. With Facebook, as soon as the HTML and CSS hits your browser it can render a more or less complete page. With Ember.js, that doesn't happen until the application is initialized and all your templates are rendered.

To be fair, that totally depends on how the application is written. You can have server-side-rendered page with single-page application, with or without Ember.js.

With Ember.js the routing framework is client-side and Ember.js stores all dynamic values in the URL fragment. The server doesn't see enough information to render a page, even if you were willing in theory to duplicate your rendering logic server-side.

Re: Advice On & Instruction in The Use of Ember.js

#62

Post by tberman »

As the guy who wrote the first bits of the Rdio code in question, it seems worth mentioning that the part in question has nothing to do with Backbone, or Ember, or anything else. That code is a cleanup function on an object that helps to abstract HTML5 vs our Flash fallback.

No matter what framework you are using, if you are solving the problems that we are solving, you are going to end up with that code.

Now, that said, I agree that learning all of the frameworks out there is advantageous, but you can't assume that the code in the blog post is indicative of anything having to do with Backbone or any other framework.

Re: Advice On & Instruction in The Use of Ember.js

#63

Post by benatkin »

benatkin wrote: post #35
skilesare wrote: post #28

I've now shipped an Ember.js application and a knockout.js application. I enjoyed ember quite a bit but feel that knockout gives me all the magic with half the complexity. It is true as the author mentions that it doesn't aim to fix the UI/statefullness issue, but I slapped on Backbone Routing on to my knockout code and it made capturing 'state' and urls a breeze. The last time I used ember was 0.9.6 and I don't thin…

I posted it as a gist on github for better formatting. I hope you don't mind. :) https://gist.github.com/3517051

Note: the author of the article (trek) posted a comment on the gist, so it's worth a look even if you've already read skilesare's comment.

Re: Advice On & Instruction in The Use of Ember.js

#64

Post by fusiongyro »

trek wrote: post #13
fusiongyro wrote: post #4

Here's my petition for the site to join the contrast rebellion: http://contrastrebellion.com/ The page is basically unreadable in FF 7.0.1 on RHEL 5.3. I realize light grey on white with a really thin font is dead sexy on your Mac (probably looks great on my home computer as well) but it's useless to me at work.

I agree. You should take this up with the Github page folks, specifically https://github.com/orderedlist . It's his template.

Thanks for changing this. You didn't have to, but it really helps, and I'm looking forward to really giving it the close read it deserves tomorrow.

Re: Advice On & Instruction in The Use of Ember.js

#66

Post by marcelvr »

tberman wrote: post #62

As the guy who wrote the first bits of the Rdio code in question, it seems worth mentioning that the part in question has nothing to do with Backbone, or Ember, or anything else. That code is a cleanup function on an object that helps to abstract HTML5 vs our Flash fallback. No matter what framework you are using, if you are solving the problems that we are solving, you are going to end up with that code. Now, that s…

Thanks for the comment. Before reading it, I admit to being lured into thinking the code in TFA was there to clean up after Backbone. Sneaky bit of writing...

Re: Advice On & Instruction in The Use of Ember.js

#67

Post by trek »

tberman wrote: post #62

As the guy who wrote the first bits of the Rdio code in question, it seems worth mentioning that the part in question has nothing to do with Backbone, or Ember, or anything else. That code is a cleanup function on an object that helps to abstract HTML5 vs our Flash fallback. No matter what framework you are using, if you are solving the problems that we are solving, you are going to end up with that code. Now, that s…

Is this entirely true? Clearly cleanup of event names like "loadedmetadata" is related to the audio element but '_bubbleProfilingEvent', '_logEvent', and general .unbind calls are on backbone-related objects, yeah?

Re: Advice On & Instruction in The Use of Ember.js

#68

Post by eddieplan9 »

sirclueless wrote: post #61
eddieplan9 wrote: post #60

Earlier quoted context omitted.

To be fair, that totally depends on how the application is written. You can have server-side-rendered page with single-page application, with or without Ember.js.

With Ember.js the routing framework is client-side and Ember.js stores all dynamic values in the URL fragment. The server doesn't see enough information to render a page, even if you were willing in theory to duplicate your rendering logic server-side.

You can use HTML5 pushState in Ember.js [1] and Backbone so application state is captured in actual URL path instead of URL location hash. The server can see enough information to render a page.

[1] http://www.kaspertidemann.com/how-to-make-ember-js-use-histo...

Re: Advice On & Instruction in The Use of Ember.js

#69

Post by skilesare »

gfunk911 wrote: post #41
skilesare wrote: post #28

I've now shipped an Ember.js application and a knockout.js application. I enjoyed ember quite a bit but feel that knockout gives me all the magic with half the complexity. It is true as the author mentions that it doesn't aim to fix the UI/statefullness issue, but I slapped on Backbone Routing on to my knockout code and it made capturing 'state' and urls a breeze. The last time I used ember was 0.9.6 and I don't thin…

That's not really accurate. There are several shorter ways to do that in Ember. App.UserView = Ember.View.extend({ templateName: 'user', }); View: {{user.firstName}} No need for the intermediate bindings. Effectively this is what you're doing in Knockout with the "content." prefix

But what are you binding to? If it is something in your controller you have to explicitly add it with the myvarBinding declaration.

Re: Advice On & Instruction in The Use of Ember.js

#70

Post by skilesare »

aidos wrote: post #49
skilesare wrote: post #28

I've now shipped an Ember.js application and a knockout.js application. I enjoyed ember quite a bit but feel that knockout gives me all the magic with half the complexity. It is true as the author mentions that it doesn't aim to fix the UI/statefullness issue, but I slapped on Backbone Routing on to my knockout code and it made capturing 'state' and urls a breeze. The last time I used ember was 0.9.6 and I don't thin…

It's a little hard to take the example seriously when you've clearly padding the Ember version with code you don't have (but would need) in the ko version.

Hmmm..I guess my point was that I don't need that code n the knockout version. In knockout the 'view' is my html template, in ember I have to have a separate class to the bind to my html. The author has pointed out that I'm using the wrong app style so I need to look back at what the are suggesting.
Post reply on HN