iamstef

o_0)

ya, we should add descriptions.

Mind opening an issue? https://github.com/emberjs/website/issues/new

As for the question:

Ember is actually built from many smaller pieces, such as:

  - container 
  - ember-metal
  - ember-runtime
  - ember-views
  - ember-handlebars
  - ember-routing
  - ember-application
  - ember
  - ember-extension-support
  - ember-testing
  - rsvp

As it turns out, you do not always need everything, so building the subset that you need totally works.

ember-runtime is made of up: ember-metal and ember-runtime https://github.com/emberjs/ember.js/blob/master/ember-dev.ym...

It provides underlying foundation, including the object model and the KVO system to the rest of ember. Leaving out views, application, routing, and many more high level ideas.

comparing angular to ember-data seems strange, no?

Although lots of work still needs to be done.

http://github.com/stefanpenner/ember-app-kit aims to prevent and mitigate the tooling pain, by having the community bear the burden.

lets just be happy about open-source. The magnitude and quality of work being contributed is amazing.

I cannot guarantee you are not hallucinating for other reasons, but yes your app should feel faster. The performance work that landed in rc3 is just paving the way for a whole class of performance improvements. Stay tunned for more!

please don't leave us hanging. I need to know what this is.

awesome :D

Although this may change in the future, our current goal is a uniform experience for our users, this includes some features not available to many or all mobile browsers, such as push notifications, photo upload, and an all around quality experience.

Currently all our executable code is bundled. We only transmit meta-data, content data and media.

I'm a developer on Yapp.

Thought some might be interested in the tech stack:

The Editor and Dashboard are built with Ember.js, which we love.

Rails on the backend, with Postgres and Redis.

We get a little help from Pusher, Transloadit and URL2PNG. The Android and iOS apps are PhoneGap with an Ember app inside.

Feel free to ask questions about our experience with any of the above.

Happy to share.

A cross-reference is only feasible in very bad situations: - no-salt or same-salt and same hashing - trivial/common passwords (password1 etc) - password(hashed/unhashed) and email are paired.

A cross-reference could be accomplished for all known cracked linkedin passwords, but this would be no different then you running a dictionary attack of known passwords against your own users... This seems very bad. Enforcing strong but sane password strength rules should mitigate this need.

Cross reference only has value if both the hash and email pairs are leaked.

The bitcoin leak fell into one of these very bad situations: - [<email>, <hash>] where leaked together - poor hashing (just sha1, no salt if memory serves) - unfortunate number of people reuse passwords

http://fuckyeahnouns.com/ycombinator Nice! Ycombinator !

woop 57 characters, now will you hire me?