# ember Published articles for ember. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Demo of a Service-Worker-Based Build Tool for Ember DevFeed: [A Demo of a Service-Worker-Based Build Tool for Ember]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2021-03-30T23:01:57Z Content type: article Language: en Sources: [Edward Faulkner]() Topics: [Ember](), [Webpack](), [Tool]() Tags: [build-tool](), [demo](), [ember](), [talk](), [tools](), [webpack]() ### AI overview This post accompanies a talk from EmberConf 2021 and presents a demo of a service-worker-based build tool for Ember. It implements enough of the Embroider v2 specification to crawl addon metadata and combine public assets, but remains incomplete and demo-quality. ### Source excerpt This post serves as a permalink to accompany my talk from EmberConf 2021. Mho The demo of the service-worker-based build tool is available here with instructions to run both the prebuilt binary (currently compiled only for OSX, sorry!) as well as how to rebuild everything yourself. It' ## Ember Table 2.0 Release DevFeed: [Ember Table 2.0 Release]() Original publisher: [Read original article]() Author: Cory Forsyth Published: 2019-08-12T17:52:23Z Content type: release Language: en Sources: [Addepar]() Topics: [Ember](), [Library](), [Sorting](), [Documentation](), [Testing](), [migration]() Tags: [2](), [datatables](), [documentation](), [ember](), [feature](), [features](), [migration](), [performance](), [release](), [sorting](), [table](), [testing]() ### AI overview Addepar announces Ember Table 2.0, a ground-up reimplementation of its data table library with a new API, improved performance for large tables, and greater flexibility. The release adds features including nested subcolumns, occlusion rendering, sorting, resizing, and interactive, versioned documentation. ### Source excerpt I'm excited to announce the release of Ember Table 2.0. This release is the culmination of more than 18 months of effort across several Addepar developers and external contributors. This release represents a ground-up re-implementation of Ember Table with a new, modern, and future-compatible API. At Addepar, the new Ember Table 2.0 ("ET2") brings even better performance on large tables and its enhanced flexibility is a better fit for the advanced use cases that Addepar clients have. Ember Table in use in the Ember Inspector extension Over the past year we've adopted ET2 into much of Addepar's product, and in an upcoming release we will have completed our migration away from the legacy version. That milestone, and the corresponding stability requirements, merit an official major release. Since this release diverges significantly from Ember Table 1.0, we renamed the original version of the library and repo to "ember-table-legacy" to make it easy for legacy codebases to continue using the older version. If you've been waiting to try ET2, now is a great time. It's a powerful and flexible data table library designed to be approachable yet full of features to accommodate complex needs, such as: fixed headers, footers, and columns row selection and sorting tree tables with group collapsing column resizing and reordering nested subcolumns (an all-new feature in ET2 that supports complex table headers, for example to create pivot tables) ability to render thousands of rows performantly via occlusion rendering (leveraging vertical-collection) compatibility with Ember versions 1.13 through 3.10, with a progressively improved API exported test object for testing tables in your app Ember Table supports sorting, column reordering, nested data, and more Additionally, significant effort went into revamping ET2 documentation. The docs use ember-cli-addon-docs so that they are searchable and versioned, with expanded sections and interactive demos. To start using the new ET2, add `emb ## Bringing the 201 Created team to Addepar DevFeed: [Bringing the 201 Created team to Addepar]() Original publisher: [Read original article]() Author: Alex Navasardyan Published: 2019-01-28T18:35:05Z Content type: news Language: en Sources: [Addepar]() Topics: [Ember](), [Tech Debt](), [Front end](), [code productivity](), [web applications](), [JavaScript]() Tags: [adopting](), [announce](), [ember](), [front-end](), [javascript](), [productivity](), [team](), [tech-debt]() ### AI overview Addepar announces that the team from 201 Created, a JavaScript consulting firm, will join the company as full-time staff. The team will help modernize Addepar's older Ember.js web application codebase and form the core of a new internal group focused on web technology improvements, best practices, and front-end developer productivity. ### Source excerpt I'm excited to announce that the team at 201 Created, a Javascript consulting firm, is joining Addepar in February. Seven months ago we asked them to help modernize Addepar's web application codebase, and now we're welcoming Matthew Beale, Cory Forsyth, Jonathan Jackson, and Kevin Pfefferle as full time staff. Addepar's original product was a Java Swing application. Seven years ago we started rewriting that application onto the web platform with Ember.js at its core. We were motivated by the promise of faster feature development, an ability to improve usage analytics, to quicken the app's loading speed, automate testing, and to provide better security to our users. When the codebase was new, modern, and smaller those promises were delivered on. But after years of a hard focus on features to ensure Addepar's adoption by the market we've accrued some tech debt. Addepar's main codebase runs on an older, unsupported version of Ember.js making it difficult to leverage the latest productivity improvements enjoyed by the wider Ember.js (and web development) community. Working with out of date software makes documentation and education a constant challenge for our front-end developers. To maintain the benefits of Addepar's original web refactor on what is now a much older and mature codebase, we're forming a new internal team at Addepar. This team will focus on practical web technology improvements, adopting best practices, and accelerating front-end developer productivity. We're looking forward to having 201 Created's team form the core of this group, and to leveraging their technical knowledge and background in pairing and training. We're excited to welcome Matthew, Cory, Jonathan, and Kevin to our team at Addepar! You'll find them and other Addepar staff at EmberConf 2019. Read more on this change at the 201 Created blog. Interested in working with us at Addepar? Visit addepar.com/careers. Bringing the 201 Created team to Addepar was originally published in Build@Addepar ## Dynamic import() into your Ember app DevFeed: [Dynamic import() into your Ember app]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2018-07-13T15:04:09Z Content type: tutorial Language: en Sources: [Edward Faulkner]() Topics: [Ember](), [import](), [App](), [Code](), [data]() Tags: [app](), [code](), [data](), [demo](), [ember](), [import](), [load](), [source](), [videos]() ### AI overview A screencast demonstrates using ECMA dynamic import() with ember-auto-import to lazily load a dependency into an Ember app. The example fetches real city data and plots it with Highcharts, loading the Highcharts code only when needed. ### Source excerpt A screencast where we build an app that loads real data, lazily loads Highcharts on demand, and plots the data using Highcharts. ## Ember 2018 Priorities DevFeed: [Ember 2018 Priorities]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2018-05-19T02:26:19Z Content type: opinion Language: en Sources: [Edward Faulkner]() Topics: [Ember](), [Framework](), [Web Development](), [JavaScript]() Tags: [contribution](), [contributors](), [docs](), [ember](), [events](), [framework]() ### AI overview An Ember community contributor outlines 2018 priorities: complete major in-progress framework features and give newer contributors more ownership and leadership opportunities. ### Source excerpt We need to ship what we started and let our newer contributors shine and lead. ## How to Add TailwindCSS to an Ember App DevFeed: [How to Add TailwindCSS to an Ember App]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2018-05-05T03:39:25Z Content type: tutorial Language: en Sources: [Edward Faulkner]() Topics: [Ember](), [TailwindCSS](), [App](), [GitHub]() Tags: [app](), [apps](), [code](), [ember](), [github](), [how-to](), [learning](), [tailwindcss](), [videos]() ### AI overview A screencast demonstrates how to integrate TailwindCSS into an Ember app. The accompanying code is available on GitHub, and the tutorial aims to address the lack of learning materials for this integration. ### Source excerpt There is definitely an intimidation factor some people feel about integrating things into Ember apps. While there are plenty of things I want to make easier too, I think a large amount of the perception only comes from lack of good learning materials. Toward that goal, I made this screencast ## Ember CLI Addon Docs: Shared Documentation for the Ember Ecosystem DevFeed: [Ember CLI Addon Docs: Shared Documentation for the Ember Ecosystem]() Original publisher: [Read original article]() Author: pzuraq Published: 2018-03-07T21:00:37Z Content type: article Language: en Sources: [Addepar]() Topics: [Ember](), [Documentation](), [code productivity](), [JavaScript]() Tags: [automated](), [developer-productivity](), [documentation](), [ember](), [ember-cli](), [emberjs](), [examples](), [experimental](), [full-text-search]() ### AI overview Addepar describes the development of ember-cli-addon-docs, a shared documentation solution for Ember addons. The project addresses limitations in existing tools by providing Ember-focused API documentation, Markdown templates, live demos, versioning, automated deployments, search, and pluggable API documentation generators. ### Source excerpt On our road to modern Ember here at Addepar, we've been hard at work developing a new component library to replace a lot of our older components, such as the now deprecated Ember Widgets library. As anyone who has built a shared toolset of components will know, one of the more tedious tasks faced by a library developer is documentation -- users of the new components need to be able to reference the APIs to know how to use them, and having a single source of truth for your docs is invaluable to developer productivity, but setting up docs in the first place is a lot of hard work! For Ember, part of the problem is that there is no standard documentation solution as of yet. The core Ember and Ember-CLI API docs use YUIDoc to generate docs automatically, but it is an aging library which doesn't have much support for modern javascript features. JSDoc is also falling behind the times lately, and newer doc tools like ESDoc and Documentation.js are still too experimental for widespread use. Moreover, none of these tools targets Ember -- they are meant for generic Javascript usage and don't highlight things that Ember devs need to know, like what arguments a component receives, what actions it sends, or what values it yields. Worse yet, none of these tools has support for live examples and demos. To get those, most addon authors resort to building an Ember app, usually using the test application (or Dummy app) included with the addon. Building an app takes time and effort, and in the end this means that very few addons in the ecosystem are fully documented with good examples and well described APIs. When we started to set up our documentation we ran into all of these issues, and we began wondering where the shared solution was for Ember documentation. As often happens in the Ember community, it turned out others had been wondering this as well! We joined forces with Sam Selikoff, Dan Freeman, and the Ember Learning team to work on ember-cli-addon-docs, a project whose goal is t ## Frameworkless JavaScript Part 3: One-Way Data Binding DevFeed: [Frameworkless JavaScript Part 3: One-Way Data Binding]() Original publisher: [Read original article]() Author: Jack Tarantino Published: 2018-02-26T00:43:11Z Content type: tutorial Language: en Sources: [Jacopo Tarantino]() Topics: [JavaScript](), [Vanilla JavaScript](), [data](), [Document Object Model (DOM)](), [proxy](), [React](), [Angular](), [Ember]() Tags: [angular](), [callback](), [code](), [developers](), [ember](), [javascript](), [re](), [react]() ### AI overview A tutorial on implementing one-way data binding in frameworkless JavaScript using native APIs, the DOM, ES6 Proxy objects, and callbacks. It explains how to update DOM content when data changes and works toward reusable node and proxy constructors. ### Source excerpt This article is one in a series about writing client-focused JavaScript without the help of libraries and frameworks. It's meant to help developers remember that they can write good code on their own using nothing but native APIs and methods. For more, check out the original article on writing small ## ES Classes in Ember.js DevFeed: [ES Classes in Ember.js]() Original publisher: [Read original article]() Author: pzuraq Published: 2017-11-15T20:01:01Z Content type: tutorial Language: en Sources: [Addepar]() Topics: [Ember](), [JavaScript](), [Web Development]() Tags: [classes](), [code](), [ember](), [emberjs](), [es-classes](), [es2017](), [javascript](), [syntax]() ### AI overview This guide explains how ES classes, class fields, and decorators can be used with Ember.js. It describes the accepted ES Classes RFC, potential benefits such as improved tooling and clearer syntax, and caveats involving currently broken features and evolving JavaScript proposals. ### Source excerpt Classes have been an emerging standard in Javascript for some time now. With features like class fields, private methods and fields, and decorators on the way, pretty soon Javascript will have a fully featured class syntax with capabilities that haven't been available in the language before. While Ember.js has had its own, trusty, custom object-model in Ember.CoreObject since the very beginning, these broader advancements are going to be the future of the language and the web itself, so in time we will have to build out and replace the existing system with one based on ES2017+ classes. If you've been paying attention to Ember RFC process you may have noticed that an RFC for ES Classes was accepted recently. The RFC was very minor: it didn't propose any overhauls or breaking changes to the Ember object model as it stands. In fact, it was really just formalizing an existing oddity -- ES classes work with Ember as is, right now, as far back as Ember v1.11 (and possibly even farther). You can use them today, along with class fields and decorators, and get the benefits of modern JS syntax, including: Better tooling from editors like VS Code and Webstorm Better static analysis tools and documentation generators, like ES Doc Shared code and solutions with a wider ecosystem, including other decorator libraries such as core-decorators Shared knowledge with a wider ecosystem -- no more needing to teach the Ember object model to new developers, they just need to know Javascript and they're good to go A simpler, cleaner, declarative syntax that's easier to understand and makes your code more readable Of course, there are some caveats with switching to classes today. Certain Ember features are currently broken and being fixed as-per the RFC. Others, like class fields, have changed dramatically, and you'll likely need to update your mental model just a bit. This guide will lay out all you need to know about using classes in Ember today, including some new techniques that add additi ## The value of a thousand little features DevFeed: [The value of a thousand little features]() Original publisher: [Read original article]() Published: 2017-04-13T00:00:00Z Content type: opinion Language: en Sources: [Robin Ward]() Topics: [Software Engineering](), [Development](), [Rails](), [Ember](), [JavaScript](), [Ruby](), [Database](), [code reviews](), [test-coverage]() Tags: [code-reviews](), [coverage](), [database](), [development](), [ember](), [javascript](), [rails](), [ruby](), [software-engineering]() ### AI overview The author reflects on five years of Discourse development, describing how the team settled on major technical choices such as Rails, ActiveRecord, Postgres, Ember.js, and JavaScript. The article also discusses codebase practices, performance improvements, and planned changes including TypeScript, replacing Sprockets, and upgrading Ruby and Rails. ### Source excerpt It's been over a year since I wrote a blog entry! And while of course the universal excuse of "I've been busy" applies, I think we reached a point in Discourse's development where we just were able to focus on the product without a lot of stuff getting in our way. I've now been working on Discourse full time for 5 years. In the beginning we had a lot more uncertainty about technical decisions. Some of the things we debated interally include: ## Strong Conventions Make Hiring Easier DevFeed: [Strong Conventions Make Hiring Easier]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2016-11-10T17:42:28Z Content type: opinion Language: en Sources: [Edward Faulkner]() Topics: [Ember](), [Learning](), [Code]() Tags: [books](), [ember](), [git](), [hiring](), [libraries](), [overhead](), [team](), [training]() ### AI overview Strong conventions and shared solutions in the Ember community can make hiring easier by reducing onboarding overhead, enabling realistic work evaluations, and helping both experienced and junior developers become productive more quickly. ### Source excerpt The most reliable way to evaluate programmer candidates is to hire them to do a bit of realistic work. This is widely understood, but not widely practiced. The biggest barrier is finding projects for them to work on. In most organizations, the overhead of getting a new person started is ## Frameworks are where we iterate on tomorrow's universal abstractions DevFeed: [Frameworks are where we iterate on tomorrow's universal abstractions]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2016-09-09T20:11:08Z Content type: opinion Language: en Sources: [Edward Faulkner]() Topics: [Framework](), [Ember](), [Programming]() Tags: [ecosystem](), [ember](), [framework](), [frameworks](), [programming]() ### AI overview The article argues that frameworks help programmers manage complexity by enabling communities to share and refine abstractions before they become broadly universal. It uses Ember's balance of stability and innovation, along with its ecosystem and upgrade practices, as an example. ### Source excerpt The amount of complexity a single human programmer can handle is fundamentally limited. Until our brave cyborg future comes, even the best programmers can only hold so much in their minds at once. And the number of programmers that can productively work on a single project is limited by the ## Watch: Ember at 10 feet DevFeed: [Watch: Ember at 10 feet]() Original publisher: [Read original article]() Published: 2014-12-22T00:00:00Z Content type: article Language: en Sources: [Robin Ward]() Topics: [Ember]() Tags: [ember](), [video](), [watch]() ### AI overview A video of the author's "Ember at 10 feet" talk from the Embergarten Saturday Symposium is available to watch. The post also links to source code and an online demo. ### Source excerpt Previously I posted notes and links for my talk about "Ember at 10 feet" from the Embergarten Saturday Symposium. Today my awesome friends at Unspace posted a video of the talk, which you can watch below: Source Code | Online Demo ## ember-tv: Creating a 10 foot interface in Ember.js DevFeed: [ember-tv: Creating a 10 foot interface in Ember.js]() Original publisher: [Read original article]() Published: 2014-11-17T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [interface](), [Code](), [repo](), [Demo]() Tags: [code](), [demo](), [ember](), [github](), [interface](), [js](), [repo](), [speaking](), [talk]() ### AI overview The article introduces a project for creating a TV-friendly, 10-foot interface in Ember.js. It describes a related conference talk and points readers to the talk's source code, slides, speaking notes, and an online demo. ### Source excerpt Over the weekend I spoke at the Embergarten Saturday Symposium, which was an awesome mini conference on Ember in Toronto. My topic was "Ember at 10ft", and it was about how to build a TV friendly interface in Ember.js. The talk was recorded but not yet posted, however I've already posted the source code on github. The github repo contains my slides from the talk as well as speaking notes. I've also put up an online demo. Check it out! ## Screencast: Using Pretender to mock a server with Ember.js DevFeed: [Screencast: Using Pretender to mock a server with Ember.js]() Original publisher: [Read original article]() Published: 2014-08-26T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [JavaScript](), [test](), [Library](), [GitHub]() Tags: [branch](), [ember](), [integration-test](), [javascript](), [js](), [library](), [login](), [mock]() ### AI overview A screencast demonstrates how to use Pretender, a JavaScript mock server library, in an Ember.js integration test. The source code for the login application is available on GitHub, with the finished version in the pretender branch. ### Source excerpt Recently I fell in love with Pretender, the mock server library in Javascript, so I decided to record a screencast showing how to use it in an Ember.js integration test: The source code for the login application is on github. The finished version is in the pretender branch. ## Screencast: Debugging an Ember.js Application DevFeed: [Screencast: Debugging an Ember.js Application]() Original publisher: [Read original article]() Published: 2014-08-16T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [debugging](), [Chrome](), [Developer Tools]() Tags: [application](), [bug](), [chrome](), [code](), [debugging](), [developer-tools](), [ember](), [github]() ### AI overview A short screencast demonstrates debugging techniques for Ember.js applications using Chrome Developer Tools and the Ember Inspector. It also links to the source code for a Bug Tracker project on GitHub. ### Source excerpt I've found that a lot of people don't know how powerful the Chrome Developer Tools are, especially when paired with the Ember Inspector. I recorded this short screencast to show a handful of tricks you can use when debugging Ember.js applications: The source code to the Bug Tracker project is on github. ## Creating an Integration test in Ember.js (Screencast) DevFeed: [Creating an Integration test in Ember.js (Screencast)]() Original publisher: [Read original article]() Published: 2014-06-27T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [Integration testing](), [Testing](), [Command-line interface]() Tags: [boilerplate](), [ember](), [ember-cli](), [how-to](), [integration-test](), [integration-testing](), [js]() ### AI overview A screencast tutorial explains how to set up integration testing in an Ember.js application with ember-cli, including the boilerplate required at the top of integration test files. ### Source excerpt Once upon a time it used to be difficult to create integration tests in Ember.js. Fortunately, the framework has come a long way and it's now really easy to get integration testing working in your application. This screencast shows how to set it up with ember-cli: There is some boilerplate code required that you'll need at the top of your integration test files if you want to do it yourself. Here it is: ## Wrapping a jQuery plugin in a Ember.js component (Screencast) DevFeed: [Wrapping a jQuery plugin in a Ember.js component (Screencast)]() Original publisher: [Read original article]() Published: 2014-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [jQuery](), [reuse]() Tags: [component](), [ember](), [js](), [plugin](), [reuse]() ### AI overview A screencast demonstrates how to wrap a jQuery plugin in an Ember.js component for reuse. ### Source excerpt Time for another screencast! This one is shorter and shows how easy it is to wrap a jQuery plugin in an Ember.js component for reuse. ## Building Emberredit (screencast) DevFeed: [Building Emberredit (screencast)]() Original publisher: [Read original article]() Published: 2014-05-29T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [App](), [Framework](), [Command-line interface]() Tags: [advanced](), [application](), [building](), [ember](), [ember-cli](), [how-to]() ### AI overview A screencast demonstrates how to build an Ember.js application without Ember Data. It converts the emberreddit project to ember-cli, beginning with a simple implementation and progressing to building an identity map. ### Source excerpt One of my more popular blog entries is on using Ember.js without Ember Data. Recently I've been going through my old entries and making sure they don't have any glaring mistakes, and I realized this would be a good opportunity to convert my emberreddit project to ember-cli. This screencast shows how you can build an Ember.js application without using Ember Data. It starts off simple and then shows how to build advanced stuff like an identity map yourself. ## The Refresh Test DevFeed: [The Refresh Test]() Original publisher: [Read original article]() Published: 2014-04-10T00:00:00Z Content type: opinion Language: en Sources: [Robin Ward]() Topics: [Ember](), [Website](), [browser](), [App]() Tags: [app](), [browser](), [ember](), [fields](), [form](), [make](), [reload](), [required]() ### AI overview The article argues that web applications should preserve form data and tolerate page refreshes. It uses frustrating account-creation and online checkout experiences to illustrate the problem, then discusses how Ember App Kit's live reloading encouraged the author to make an application refresh-resistant. ### Source excerpt How many times has the following happened to you? You go to a web site and it asks you to create an account. You fill out a form with all the obvious fields and hit submit. The page refreshes and shows you the form again. Phone Number is required Well, that's annoying. There was no indication that the site needed your phone number. You prefer not to give out your phone number to every web site, but this one is run by a company you trust, so you scroll down and fill it out. You submit the form again. ## Hiding Offscreen Content in Ember.js DevFeed: [Hiding Offscreen Content in Ember.js]() Original publisher: [Read original article]() Published: 2014-01-04T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [browser](), [Document Object Model (DOM)](), [render]() Tags: [browser](), [elements](), [ember](), [js](), [memory](), [render]() ### AI overview This article explains how hiding offscreen content in Ember.js can reduce the browser's DOM workload and memory use. It describes Discourse's infinite-scrolling performance problem and a cloak technique that replaces offscreen views with simpler elements while preserving their height. ### Source excerpt Everything you render in a browser, whether it's a blog post or a tweet or a video, has a performance cost. At the very least, you will be asking the browser to render a handful of tags and text elements that make up your user interface. That structure, a subtree in the browser's DOM, can be quite complicated and memory intensive. The more tags and elements you render, the slower the browser is going to perform, and the more memory it is going to use to do it. It follows that if you give the browser less work to do, it will do it faster. ## Internationalization Support in Ember.js DevFeed: [Internationalization Support in Ember.js]() Original publisher: [Read original article]() Published: 2013-11-24T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Internationalization (i18n)](), [Ember](), [JavaScript](), [Rails](), [Web Development]() Tags: [client](), [ember](), [framework](), [function](), [i18n](), [javascript](), [library](), [parameter](), [rails](), [server](), [templates](), [translation](), [web]() ### AI overview A tutorial explains how to add internationalization to an Ember.js client-side application using i18n-js. It describes using Rails built-in i18n support on the server, including translation data in an application, exposing translations through a helper for Handlebars templates, and handling pluralization parameters. ### Source excerpt One thing I'm really proud of is that when we launched Discourse, we had first class Internationalization (i18n) support ready to be used. Our first release only English, but thanks to our community we have 18 localizations of our software in progress! Here's what Discourse looks like in Simplified Chinese: On the server side, Discourse uses Rails' built in i18n support. It has been around for a long time and works easily so I won't go into that. Check out the documentation for your server side framework of choice for more. ## Computed Property Macros DevFeed: [Computed Property Macros]() Original publisher: [Read original article]() Published: 2013-07-07T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [Caching](), [Handlebars](), [conditionals](), [functions]() Tags: [caching](), [conditionals](), [ember](), [functions](), [templates]() ### AI overview This tutorial explains how Ember computed property macros can simplify computed properties in applications using Handlebars templates. It describes their use as shorter, clearer alternatives for common computed-property patterns and notes that they can reduce repeated property names while supporting cached intermediate results. ### Source excerpt Computed Properties By design, Handlebars templates don't allow complex expressions. You are given an {{#if}} block helper, but it can only evaluate whether something is "truthy" (aka true, a non-empty string or array or other value that is not undefined or null.) For example, you can't do something like this: {{#if (eyes.length == 1) && (horns.length == 1) && flies && (color == 'purple') && eatsDudes}} It was a one-eyed, one-horned, flying purple people eater! {{/if}} Handlebars encourages you to use a single evaluation for your logic: ## AngularJS vs Ember DevFeed: [AngularJS vs Ember]() Original publisher: [Read original article]() Published: 2013-06-15T00:00:00Z Content type: comparison Language: en Sources: [Robin Ward]() Topics: [Angular](), [Ember](), [mvc](), [Framework](), [Stack Overflow]() Tags: [angularjs](), [ember](), [javascript](), [mvc]() ### AI overview An experienced Ember developer investigates why AngularJS is gaining developer mind share and argues that its relative simplicity makes it easier to learn. The article cautions that simplicity is not always good design and may be a poor fit for ambitious, long-lived applications. ### Source excerpt Recently I got together with some local developers to discuss client side MVC frameworks. We ended up discussing many of the differences between AngularJS and Ember. Discourse is an Ember application and has been since the first prototype, so I have a lot of experience with it. However, it became clear during the conversation with my peers that there was a lot about AngularJS I didn't know. There is evidence that AngularJS is beating out Ember in terms of developer mind share: there are more Stack Overflow questions dedicated to AngularJS. AngularJS has more stars and forks on Github. At a recent Javascript meetup in Toronto, when polled virtually every developer expressed interest in learning more about AngularJS. Clearly there is something to this framework! [Next page]()