Open-sourcing OvertureJS – the JavaScript lib that powers FastMail (opens in new tab)

I'm hoping to be able to release Cyrus 2.5 soon. We just rebased the FastMail branch on top of the current master tree and rolled it to 2% of our users with no issue - it was months behind until recently. Planning to roll that out to everyone very soon. I've been testing it just with a few of my own users and patching issues for the last month.

Speaking of Cyrus - are there OSS push IMAP servers these days?

The other side is that it does take a not-insignificant amount of time and effort to prepare a fifteen-year-old codebase for the public. There's got to be some benefit to the business to make it worth that.

The old web framework that we use is good for what it is, and we understand it, but its not state-of-the-art by any stretch, it does some weird things that aren't good practice in "modern" Perl, its still fairly heavily tied to Apache2/mod_perl and other parts of our internal libs, and so on. We don't use it for new code ourselves and we're actively migrating everything written in it onto Overture-based UI.

So given that even we don't want to use it and the off-the-shelf Perl web frameworks are generally better, it really doesn't help anyone to make it open source.

That's not to say there's nothing in our system not worth open-sourcing. For example, we've deliberately written our CalDAV/CardDAV libs in a nice clean modular way because we've planned to release them from the very beginning. Its just some things, like the web framework, that have no particular value.

I'm not op, but I switched to fastmail for my family hosting a year ago. I was driven away because of the continual UI changes Google were making. I don't want to re-explain the interface to my mum every three months. Fastmail has nice buttons with words on - when I switched the first conversation I had was "so how do I send an ema… oh there it is!"

Also fastmail is faster! You get email, contacts and file storage. If you are on the $40/yr plan you get caldav support as well. Works very well on all my devices.

Only downside is spamassassin isn't as effective as gmail's spam filters, but I no longer have to cope with mailing lists being marked as spam by the masses who can't work an unsubscribe button.

On that note, you can also write your own seive rules for filtering, and there's the 'if matched stop running filters' option that is so glaringly absent from gmail.

So I'm a happy customer.

I am on the trial for 60 days, which is the equivalent of the $40 plan. Barring some disaster I will pay for the $40 plan.

I switched because I recently purchased several domains and needed a mail system for them. Google Apps isn't free anymore, and the free email forwarding from my registrar just expired.

I will still keep my personal emails on Gmail for now, mostly because I love Mailbox.app too much.

Downsides; filtering sucks compared to gmail, keybindings aren't gmail

My experience has been that performant code is very hard to write. In particular, the tools that Angular provides for the most common sorts of things you'd want it to do (ng-repeat, ng-show/hide, ng-click, $on and $watch) all break down for one reason or another when trying to use them in anything but a toy application [0].

When I realized that ng-hide just applies CSS classes I did a huge facepalm. Consider the example of dynamically constructing a table. In Angular:

    <tr ng-repeat="child in children">
      <td ng-show="foo(child)">Foo</td>
      <td ng-hide="foo(child)">Bar</td>
    </tr>

This example runs the function foo four (!) times per digest cycle per item. Sure, you could convolute your code to make the Angular more performant, but at the cost of clear and maintainable markup. What's more, this produces rows with two cells, one of them hidden with CSS, which is ripe for creating hard-to-debug issues. The alternative in basically any other framework is written in a way and produces code execution and markup that you'd intuitively expect.

Angular's directive system encourages developers to write illegal markup. Enough said.

Angular's DI system is needlessly complicated, and the basic usage breaks when minifying because it couples identifier names to string values.

That same issue is repeated in many different aspects of Angular: the basic, intuitive usage is (intentionally or not) broken in a production environment. The amount of deep knowledge of the Angular framework that's required to successfully develop apps is absurd.

[0]: https://www.airpair.com/angularjs/posts/angularjs-performanc...

@couchand I am also interested why you are migrating from Angular

install Firefox mobile, go to the jsperf link on the article.

Firefox mobile is still ignored in San Francisco bubble, but it's gaining rapid adoption on influencers... I'm putting all my money on it being everyone's browser in the next years. it will take everyone by surprise just like chrome did when it was faster.