_____s

I've been using Notion for quite some time now. It's pretty neat although I wish it was (a) faster and (b) had a better writing experience. I find Dropbox Paper to offer the best writing experience but Notion is unbelievably flexible, so I use it instead.

Unless you absolutely need to integrate with the payment provider, release it and work on the payment integration after that.

I've been in the same position. For me, if I'm working on a substantial project solo, one great source of motivation is when people are using it, giving me feedback, etc. So when you have actual usage, some momentum, it's (generally) easier to keep going. The more time goes by without actually releasing something, the easier it is to lose momentum.

Also, if you really don't like a provider, it's generally not worth your time to use them. You will end up spending some time maintaining in the future too and you will resent it, so probably better to find something that's good to work with.

Customer.io will come pretty close! Fully remote, great team, great culture. I've only recently started working here, but it's been a great place to work. Their interview process was also the best I've come across so far.

I think, for the quality, it's on the lower end. Most such services that I subscribe to (or have in the past) are $20-30 per month. The quality of both the production and content is easily worth the money. Even more so now that there are 4 seasons of some really high-quality screencasts from the past.

The value I've personally got out of DAS is incredible.

One of the things with a large framework is that moving to a completely new direction is more challenging than it looks. So, at times, ember has made unrealistic promises — and Yehuda alluded to this in the keynote — but one can learn from it and get better.

As for Fastboot, it has its edges but there are people using it in production (DockYard is one, if I'm not wrong). ember-engines also says it's experimental and it does have some missing stuff (from my experience) but what is there works well.

Some of the things perhaps needed a rewrite of the underlying architecture. One great thing about ember (apart from v 1.13) has been just how painless it has been to upgrade. All the major changes they have made have largely been drop-in. Getting to that kind of backward compatibility is also a pretty impressive feat considering how big it is.

So, all in all, I agree that some of the things were overhyped and unrealistic but it seems they have learned from it, and I think that's just fine.

With Glimmer as a standalone library, I think ember's going in the right direction. There's been some excellent work on Fastboot and Engines in the last year or so and I really like the approach ember's team is taking with this.

React, for me, still offers better composability. You deal in plain JS objects, pass them around, and can build really complex UIs on top of that. I also really like redux. I still use ember heavily though; I think we'll get there as well!

Another great thing about ember-cli is that it has very quickly build around it a great community [1]. There are a lot of high quality, well tested addons that are easy to install and use, and it's easy to create your own as well.

[1]: https://emberobserver.com/

The first thing I'd do is e-mail people who are cancelling and ask them the reason. Upselling current customers doesn't really stop the churn, and a 50% drop rate means there's something seriously wrong. Asking people nicely will get you a lot of answers, especially when there are so many people cancelling.

I'd give it a chance. They may have made poor decisions earlier, but there's a good chance they know that, too, and they would have learned from it.

A newer framework from the same people has at least one thing going for them: they aren't likely to make the same mistakes.

A very poor precedent has been set, unfortunately.

No, actually, there were quite a few new introductions between 1.11 and 1.13 (Glimmer, the new rendering engine; Actions and API changed, ED became 1.0, got more stable), and, as a result, there were numerous deprecations in the 1.13 release. 2.0 removes things that were deprecated in 1.13. Things like views, active model adapter, etc. have been extracted out in an addon.

None of these things broke the API; there was always a sane (although sometimes painful) process to help you through the upgrade. There are other things planned for the next few releases, such as routable components, new component syntax, etc. but the things they will replace (controllers and the old component syntax) will be supported through the 2.0 cycle (at least that's what's said).

Ember's deprecations in 1.13 were a bit of work for me, as a developer, but the new features in the past few months have done a lot of good to the framework and removed a lot of the complexity. I much prefer this way of upgrading, and I really, really appreciate the Ember team for doing it this way.