We use mirage with test-controlled response timings to be able to acceptance test loading states. Works great.

You can also configure a universal delay if you’re using mirage in development and want to get a feel for your app with a certain amount of latency.

<Raises hand> Took about a developer day to fix everything. Drag/drop list reordering, pan/zoom image cropper were the primary things busted. IMO, the change was an unacceptably aggressive move by the Chrome team made with good intentions.

> Drag/drop list reordering, pan/zoom image cropper

I'm curious, were these implemented using a 3rd party library or developed in-house?

It broke our web apps. Specifically, drag and drop list reordering functionality and image cropping. I was pissed when it happened. It wasn't a change that a typical content site would be broken by, but a lot of web apps were: drag/drop reordering isn't a very unusual feature these days.

What we do is process a check in our admin which hits Stripe's API to create the customer if necessary (no payment source necessary when doing this via API in our experience) and then adjust the customer's account balance by the amount of the check. Then we process the customer's subscription and Stripe automatically debits the customer's account to pay the invoice.

I was there live for this presentation. It was epic. Fun, but also very level-headed. I learned a lot.

If you can get away with that, it's certainly a way to reduce complexity. However, providing in-flow auth without a page reload is undoubtedly a nicer, faster experience. This library seems like a good way to lower the effort for Ember app developers.

Hey Sold team... do you have any lessons learned to share with the community?

I don't work for Sold, but I think the #1 thing you should consider is how you brand your company to make it attractive for acquisition. A good name can go a long way.

Agree. The router needs a little more power and then 1.0 will be pretty sweet.

Yapp is built on Ember and it has been a joy. Terrific community and a lovely layered design that lets you work at the level of abstraction appropriate to the interaction you are building. We have ember-data in production in selective places, and it definitely has a ways to go to deliver on its full promise. That said, you can't really build an ambitious app without some model/persistence concepts, or without an identity map, so it is a big win for that already.

The common refrain that I hear talking to people in NYC and the wider internet world is that people want Ember what Ember promises and has begun to deliver. More and more of those folks (including my team) are rolling up their sleeves to help make it fulfill its promise.

If Coffeescript is an alternative to Javascript, then yes. If not, no.

Exactly. Emblem.js is for people who love Haml / Slim / Jade and want to use that style of templating with Handlebars.js

It really fits into place if you're coming from one of those libraries. I only wish I could enable percent-sign indicators for HTML tags! (%h1 vs h1)

%h1 is totally valid emblem syntax.

edit: it's optional, of course, but you have to use it if you need to use non-standard (read: unrecognized by emblem) html tags

Not sure how I missed that. It's a kick-ass little feature in my book, because while I appreciate the "implied HTML tags", I do find them easy to miss.