To those inspired by this achievement to look more into polar expeditions, I can highly recommend Michael Palin’s “Erebus”. It’s a riveting read on the challenges, successes, and tragedies of the British explorer ship Erebus, its commanders, officers, and crews.
Apologies if this is incorrect (on my phone atm) but I've been using <space> as leader for two years now, and have never ever noticed lag in insert mode.
Perhaps it's a setting you have enabled/disabled, or unrelated to vim?
This lag is introduced by vim, to wait for the next keys and see if you are actually inserting them or using mapped key sequence.
It is configurable in vim, but then either you have a lag and you are able to use your key sequence, or you don't and <leader> sequences cannot be used.
So maybe I have something configured that sets it wrong, but I do not see how to reconcile both things.
Unless you’re deliberately enabling certain key mappings in insert mode, then yes you’ve configured something wrong. And if you have deliberately enabled these bindings, you’re probably misunderstanding Vim.
The whole point of Vim’s normal mode is to free up “modifier-free” key mappings for commands rather than inserting characters. So by extension, using “modifier-free” key mappings for commands in insert mode is a Vim anti-pattern (if you want custom mapping’s in insert mode, use mappings for them with modifier keys).
Regarding your issue, I suspect your defining your bindings with the `map` keyword when you should be using `nmap` (or better yet `nnoremap‘).
The multi-touch extension sounds amazing. I went to try it, but it doesn't seem to work. I see the little dialog in the bottom right corner when I have my fingers on the trackpad, but nothing happens on keystroke.
It's mostly definitely due to the recent update to Sierra. If you do use Sierra, have you managed to make it work?
From El Capitan Apple have been "courageous" enough to essentially disable many of the most useful apps with some of their new "features". I still use El Capitan, so I have yet to deal with the Sierra issues, however I have heard that Karabiner-Elements (https://github.com/tekezo/Karabiner-Elements) is progressing nicely, so you could try that.
It's fascinating how brilliant this solution is. Let it slowly bounce on the comet, so that the rebounce velocity is very low, it doesn't affect the comet trajectory in any way, and they're collecting data during the slow descent. Nice.
Rosetta couldn't really affect the comet trajectory in a meaningful way, even if we wanted to. The comet has a mass of nearly 10 trillion kg, the orbiter is <3000 kg, and P = MV. It would need to have insane velocity to impart any meaningful momentum.
This looks incredible, congratulations to the Elixir team!
Perhaps more exciting than the first part of the post is the second bit about the future. It's fantastic to see such a clear path forward for concurrency in Elixir. Definitely looking forward to GenStage.Flow
Another thanks to the teams behind all these amazing releases, and particularly (for this news) Phoenix.Presence and Phoenix.PubSub, for the wide range of new exciting applications they'll have.
Just bumped my servers to erlang 19, Elixir 1.3 and Phoenix 1.2. The erlang and Elixir communities have done a great job shipping.
At my organization, I created our first internal service which uses Elixir and Phoenix. I've had a number of both junior and senior devs come up to me really excited about building on Phoenix and Elixir. It's rock-solid stable, fast and fun to use. Props to José, Chris and the rest of the team for their continued hard work.
I won't say testing HiPE with fibonacci is silly because this is exactly the kind of numerical computation where we expect HiPE to be useful: it looks like it is :-)
