Node.js Launches Official Community Space on Discord
We know that building your apps on top of a framework requires
trust, and that trust is never put to the test more than when security
vulnerabilities are discovered.
While we're very fortunate to work on an open source project that runs
in a sandboxed environment, the browser, we realize that even JavaScript
applications can be vulnerable to attacks from malicious third-parties.
Today, we're releasing the second Release Candidate of Ember 1.0.
As we said when we released RC1, the next few releases will be
about bugfixes and improvements, and should not have any breaking
changes.
Namespace Lookup for Controllers
It is now possible to look up controllers that are included in a
namespace other than the main application namespace.
For example, when using the render helper:
Yesterday, we gave you an update on our progress making Ember.js easier
to use. One thing we didn't discuss was our plan for Ember Data.
It's no secret that, while many developers are building awesome apps
with Ember.js, Ember Data still causes lots of frustration due to bugs
and a changing, complex API. Documentation about it is also mixed in
with Ember.js documentation, making it difficult for new developers to
understand what is stable and what is not.
We frequently receive feedback from new developers about how frustrating
it can be to get started with Ember. Yesterday, one of the most active
comment threads on Hacker
News was largely about that.
We hear you loud and clear. Ember.js is not easy to get started with, and we take that very seriously. We are all working nights and weekends to make the framework as approachable as humanly possible.