From the web page: Dragonfly is an in-memory data store built for modern application workloads. It is fully compatible with the Redis and Memcached APIs, required no code changes to adopt
Reproducibility and peace of mind! There's nothing worse that getting woken up at 3:30 AM and realizing that it'll probably take a few hours to rebuild a server because it's dead and not coming back.
When infrastructure is code, you just spin up a new machine...no thinking involved. Also, since you're used to deploying this way, the process is smooth and as quick possible.
When you build the server by hand...you're often searching around for old ssl certificates, installing packages you forgot were dependencies, etc. Takes a long time to get it right.
If you're skeptical of the cost/benefit of the approach, you realize really quick that it's worthwhile when stuff starts to fail. Especially if it happens more than once.
Check out enpass. Small, one time payment per platform. (Free for certain usage). It is a native client that supports sync. It also works well cross-platform, including linux. The mobile clients are also good.
I don't think the intent is to do code review from email. The idea would be to send the merge request through email, which is then imported into your local git as a branch. Then you're able to do review/analysis/etc with whichever git tooling you prefer.
Yes and no. I generally don't recommend emacs to everybody by default because I've come to realize it's not what everybody wants. Until people want to have a powerful, customizable editor I recommend something pretty and user friendly. Perhaps sublime text, where they can ease into being productive.
That said, I do definitely recommend it to people on a case by case basis (Power users, command line gurus, mouse haters, etc). Those who make it over the initial learning hump tend to really love it.
Not necessarily the full story. I have set my preference to text email over html email in one client that I use. This is at least one example of a client making the decision before opening the email.
I am both comfortable with git on the command line and through emacs. I prefer magit mostly because of its contextual support. With the command line, each command can derive no context from the last command. With magit, it's easy to drill in and see more relevant data (or edit that data) quicker and easier.
Just wanted to point out that not everybody is merely looking for an easier experience, or one that looks prettier.