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

Ember.js 1.0 Released

emberjs.com

Post reply on HN
Print view View original

61–70 of 104 posts

Re: Ember.js 1.0 Released

#61

Post by arms »

tomdale wrote: 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…

Thanks for sharing this video. It's been awhile since I checked out Ember, but this video would've been a great resource early on. I'm happy to see that it'll provide a high level glance of Ember to people deciding on a JS framework to use.

Re: Ember.js 1.0 Released

#62

Post by outside1234 »

Congrats! I'm been using Ember for over a year and I love it.

My protip for the newbie is to go install Yeoman, then install the generator (npm install generator-ember), and then you can scaffold out a project as easily as (yo ember), and build a minified version as easy as (grunt build), and have a live updating version of the site as easy as (grunt server).

Re: Ember.js 1.0 Released

#63

Post by mjallday »

programminggeek wrote: post #51

After building some single page JS web apps small and large, I am not sure that building large JS web apps is actually a good idea. In fact, a lot of the time they probably aren't a good idea. It is often better to just build out separate pages and on a page that requires more interactivity, use knockout or something similar.

What are the issues that you've run into?

We've used Ember.js to build a reasonably complex app (github.com/balanced/balanced-dashboard) and while there have been some tricky bits it's generally been what we expected it to be.

Ember.js does a great job of helping you when you start to get a lot of moving parts. I felt the same way you did before I dived in but now I'm comfortable in saying that its possible to build large apps in JavaScript.

Re: Ember.js 1.0 Released

#64

Post by jonnii »

gavinjoyce wrote: post #39
eknkc wrote: post #36

I've been developing on AngularJS for a while now, and have been constantly checking Ember's development. I happen to like a lot of stuff in Ember and meant to use it in production. I mean, I really want to use it! However, it took forever to reach this state. It was always beta, rc or some other non-production version, in rapid development with API changes and stuff. While this is great news that it's finally a stab…

> It seems that Ember Data is in a new round of development with alpha status Ember Data isn't a requirement of Ember by any means. You can happily use these instead: * jQuery.ajax * https://github.com/ebryn/ember-model * http://epf.io/ * https://github.com/zendesk/ember-resource

And Emu:

* https://github.com/charlieridley/emu/

Re: Ember.js 1.0 Released

#65

Post by mjallday »

Kudos wrote: post #14
Cieplak wrote: post #8

If you want to see ember in action, you can see how we use it in production: https://github.com/balanced/balanced-dashboard It has been a great tool in our toolbox, and we really feel the benefits of all the hard work and brilliance driving ember.

How come you guys aren't using push state? Does Ember not provide it in its routing?

We have an open issue, https://github.com/balanced/balanced-dashboard/issues/370 , that documents what's blocking. We were using iframes for backwards compatibility while we migrated from a regular HTML dashboard to our new Ember.js one.

We just removed the last iframe page (yay!) last week so I think we can finally get around to doing this!

Re: Ember.js 1.0 Released

#67

Post by zwily »

erikpukinskis wrote: post #29
noelwelsh wrote: post #9

So, isn't it time we had another Angular vs Ember discussion? I tried Ember some time ago and it just didn't click for me. It's hard to explain exactly why, but I found myself switching between too many files to get simple things done. I've done some simple Angular work recently, and found it a relatively simple system. In defence of Ember everything about the project -- docs, community -- seems to be better organise…

I've been working in Ember full time now for a few months, and I really advocate using just two files, at least to start: one for Javascript and one for HTML. I know, it's a terrible, horrible practice, but hear me out. Learning Ember, especially at the beginning, required me to sort of rewire my brain about what goes where. It's "MVC", but the M, V, and C mean totally different things than they mean in Rails. Really…

I wrote the first ~25% of my first few Ember apps completely in jsbin. The ease of starting and sharing what I'd done with others was great.

Re: Ember.js 1.0 Released

#68

Post by impressive »

At work we have been using Angular for about a year and we had evaluated Ember and decided not to use it because it wasn't really as good at the time. It may be better now, but I'm not as excited. Here's why:

1. For most applications, the JS MVC framework needs server-side backing, so don't fool yourself: You are no longer using MVC- you are using MVC X 2. There is no magic server-side out there that runs on self-generated jellybeans and weed that will power these frameworks. They are beautiful but unnecessary cruft in such pretty packaging that you think they are doing you a favor and washing your clothes for you. But they are only washing part of your clothes. The rest are still dirty and on the floor.

2. Despite the old saying, "Everything at some point will be written in JavaScript," it is not JavaScript, but rather mobile application development that is leading the charge in the development world currently. It is the platform and the accessibility (intuitive, easily held and portable), and not the "how" (whether it is webkit running Ember or Angular).

So, even though it is awesome that Ember and Angular are great, and I'm happy for you Yahuda, just like I'm happy for Misko/Igor/Vojta, I think this is a lot about only part of a solution, and it might not even be the right one. The whole package and the platform must be considered, not just the web client UI.

So, I ask, now that v1.0 is out, what is being done about considering the ease of developing the entire shebang?

Re: Ember.js 1.0 Released

#69

Post by SkyMarshal »

sambeau wrote: 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…

We've got more than two. Facebook's React, and Ractive.js, and the old stalwart Knockout.js to name a few.

http://facebook.github.io/react/

http://www.ractivejs.org/

Re: Ember.js 1.0 Released

#70

Post by bsimpson »

tomdale wrote: 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…

Around what time did this reboot occur? I remember being impressed with what you were working on when it was still called SproutCore 2, but it was so hard to follow, I ended up taking Handlebars RC3 and writing my own JS layer.
Post reply on HN