Live data from Hacker News

Ember.js 1.0 Released

emberjs.com

91–100 of 104 posts

Re: Ember.js 1.0 Released

#91

Disclaimer: I am a backend developer sporadically doing front end to speed things up (as in: back end is done, time to help the other guys with the front end). Why is this better than jQuery? I haven't looked at the full code base and documentation but did watch the 25 min demo video posted in this thread and thought: "Well, I can do all of this with jQuery too probably just-as fast.". What makes this different? Am I…

It depends on the scale of the project. If what you want to do can be done with 200 or 300 lines of JavaScript using jQuery, then fine. Go for it!

But I've seen codebases with over 10,000 lines of JavaScript, using only jQuery, and it isn't a pleasant sight. You either end up writing your own ad-hoc framework to add structure, or, more likely, you end up with a bug-ridden, unmaintainable mess where you're writing basically the same code over and over. A framework like Ember or Angular provides structure and takes out a lot of the grunt work of making a large, single-page app.

Re: Ember.js 1.0 Released

#92
post #6

I said this already on Twitter, but: It’s been 2½ years since I started working on Ember.js. While I’m proud of the code we wrote, I’m even more proud of the community we built. We have been lucky enough to attract the companies and individuals that are tackling the hardest problems in developing 100% JavaScript web applications; people for whom the only acceptable answer is solid engineering, not piles of hacks. As…

Good work Tom, Yehuda, and team. I had very difficult time recommending Ember during the transition phase (mostly because the router was impossibly difficult to understand). I wanted to like it so bad, and now I finally think I can. I'm going to reboot the project I was working on and give Ember 1.0 a shot.

Re: Ember.js 1.0 Released

#94
post #50
post #20

Let's not use this opportunity to start another Ember vs Angular argument. Can we instead take a moment to celebrate the fact that we now have two major, stable, fast, capable, testable, tested, supported, documented, git-hubbed single-app javascript frameworks with large, passionate communities. Let's also recognise and celebrate the hard work put into these projects by the Ember & Angular teams. Ember and Angular a…

Since when did Backbone not count as a major framework?

Ember and Angular are cars, Backbone are sneakers.

Re: Ember.js 1.0 Released

#95
post #47

I sorta learn Angularjs, well went through a few tutorials on Angular for a company. Turned out that company is now doing emberjs and I have to learn emberjs. I have to say EmberData is not production ready. It's modularity is more monolithic compare to Angularjs. There's a lot of moving parts that can break (in term of using emblem, brunch, handlebar, etc...). And the community is much smaller, less books, less peop…

comparing angular to ember-data seems strange, no?

Well my reasoning is because angular have a so called model. It's scope.

Angular doesn't need a model, it's a MV whatever. Where as ember is MVC. The framework is MVC and it's M is not complete at all. So judging from an overall framework ember is not complete in that respect where as Angular is.

Like come on, 1.0 and hey our M in our MVC framework is incomplete. Um... that's shouldn't even be 1.0. 1.0 to them is the api is going to be stable but not the emberdata, the model. Really?

Re: Ember.js 1.0 Released

#96

Disclaimer: I am a backend developer sporadically doing front end to speed things up (as in: back end is done, time to help the other guys with the front end). Why is this better than jQuery? I haven't looked at the full code base and documentation but did watch the 25 min demo video posted in this thread and thought: "Well, I can do all of this with jQuery too probably just-as fast.". What makes this different? Am I…

Ember is a framework, jQuery is a library. jQuery doesn't really give you much of anything that you don't have in regular JavaScript, it just makes things a bit more concise and smoothes over some browser inconsistencies. Ember provides you with a structure for your application, two-way binding, a template language (Handlebars), a router, and many other things. It's not better than jQuery, it's a completely different type of thing.

Re: Ember.js 1.0 Released

#97
post #47

Earlier quoted context omitted.

comparing angular to ember-data seems strange, no?

Well my reasoning is because angular have a so called model. It's scope. Angular doesn't need a model, it's a MV whatever. Where as ember is MVC. The framework is MVC and it's M is not complete at all. So judging from an overall framework ember is not complete in that respect where as Angular is. Like come on, 1.0 and hey our M in our MVC framework is incomplete. Um... that's shouldn't even be 1.0. 1.0 to them is the…

o_0)

Re: Ember.js 1.0 Released

#98
post #47

Earlier quoted context omitted.

comparing angular to ember-data seems strange, no?

Well my reasoning is because angular have a so called model. It's scope. Angular doesn't need a model, it's a MV whatever. Where as ember is MVC. The framework is MVC and it's M is not complete at all. So judging from an overall framework ember is not complete in that respect where as Angular is. Like come on, 1.0 and hey our M in our MVC framework is incomplete. Um... that's shouldn't even be 1.0. 1.0 to them is the…

Ember.Object is the M in the Ember.js MVC framework. Ember Data is a library to synchronize a RESTful API with your models, without ever writing a line of networking or AJAX code.

Re: Ember.js 1.0 Released

#99

For the uninitiated, could someone please explain what we use Ember (and related frameworks like Angular.js) for? For example, I build a Rails app to handle models, views, and controllers on the backend. Then I can use HTML/CSS/JS to write a frontend to interface with the Rails app. Why do we need another MVC framework on top of Rails?

When writing a single-page app you only need a RESTful API on the backend, much like developing for mobile, to sync your models from the client. Ideally, the models would be shared between client and server without the need for duplicating code. There has been a few steps in that direction in node.js, but it's an ongoing problem that hopefully we'll figure out in the next couple years.

Thanks for your response.

To clarify, when you say RESTful API, do you mean the client-side MVC framework issues API calls to a server which then updates the backend (database?).

I guess this model is client-centric while the typical Rails app is server-centric (MVC logic executes on the server and then serves the relevant HTML/CSS to the client).

Any particular advantages to the client-side framework over the server-side framework?

Re: Ember.js 1.0 Released

#100
post #20

Let's not use this opportunity to start another Ember vs Angular argument. Can we instead take a moment to celebrate the fact that we now have two major, stable, fast, capable, testable, tested, supported, documented, git-hubbed single-app javascript frameworks with large, passionate communities. Let's also recognise and celebrate the hard work put into these projects by the Ember & Angular teams. Ember and Angular a…

> Let's not use this opportunity to start another Ember vs Angular argument.

So are you mentioning Angular.js then? If you are going to celebrate Angular 1.2 wait for the Angular 1.2 announcement and post there. Sounds like "I don't want to troll but I will anyway while telling everyone I don't want to".

Post reply on HN