Is anyone developing on ExpressionEngine in 2015? [updated]

Original article from Michael Aleo, on Twitter:

Is anyone developing on ExpressionEngine in 2015? Is there any reason to still consider it at this point?

That first question is one I'm burning to know the answer to. Strategically, I feel they've got so much wrong and are at risk of becoming irrelevant in the CMS space. But the fact is, I know nothing. This reply from EllisLab, the owners of ExpressionEngine supports my view, though:

Would love to know your pain points, but the #eecms community is quite active, and still making clients happy.

Quite active? Still making clients happy?

Update (2nd April 2015): At least a handful of people have responded and told me they're actively developing with ExpressionEngine. I get the impression this is with new projects, as well, which I find puzzling. Having tried ExpressionEngine's competition, I just can't justify developing in ExpressionEngine any more. I've got two more burning questions for these people:

1. Have you seriously explored any alternatives?
2. If so, what advantage does ExpressionEngine have that keeps you coming back to it?

Update (7th April 2015): The main answer seems to "If ExpressionEngine does what I want it to, why bother learning anything else?" I'm not going to argue with that.