kerny

Any third party code can just read your credentials file and POST it to remote server.

When you see majority of consultants from the biggest Linux company (that also focuses on desktop Linux) using Macs for their work, you know that Linux on desktops won't happen anytime soon.

They could have used: soft, hard and strict with the documentation explaining the differences.

can you expand a bit more on "not as clean" as NeoVim? I consider vim's implementation of async jobs simpler than neovim's.

No OP, but IMHO GitLab is getting quite heavyweight and that's why people are looking for more lightweight alternatives.

This diagram is not entirely correct.

The remote bash startup order is further complicated by the existence of a compile time flag SSH_SOURCE_BASHRC. This flag determines if a remote non-interactive shell will load the ~/.bashrc file.

This flag is turned off by default and stays off in some distributions (like Archlinux), but is turned on in others (Debian, Fedora, ...) to replicate very old rsh behaviour.

9) The remote bash startup order is further complicated by the existence of a compile time flag SSH_SOURCE_BASHRC. This flag determines if a remote non-interactive shell will load the ~/.bashrc file.

This flag is turned off by default and stays off in some distributions (like Archlinux), but is turned on in others (Debian, Fedora, ...) to replicate very old rsh behaviour.

> That's can happen to bitcoin, as its a fixed supply.

There's endless ways to compute arbitrary numbers.

Can you back up this claim? I think it's not true and authors of both projects respect each other. They simply have different views regarding backwards compatibility etc.

Which metropolis are you talking about?

Why would you leave such a great place to work?

> The're VM's

They are definitely not VMs.

> But they're really, really efficient compared to VM's.

I think that the virtualisation CPU overhead is below 1%. Layered file systems are possible with virtual machines as well so disk space usage could be comparable.

What do you mean that they are "really, really efficient" ?

Why is it bad? Competition is always a good thing, and I'm glad that Neovim urged Braam to improve Vim as well.

Personally, I'll rather use Vim as it focuses on stability and long-term compatibility. I have a huge respect for Braam for maintaining the project for so long. On the other hand, some of the Neovim's promises are just that, big dreams. Development on Neovim has slowed down and if you look at their git history, you'll see most of their commits are actually upstream patches taken from Vim.

I also see a lot of hate towards Vim source code and code styling, which is not that bad and I actually prefer it to Neovim's two spaces per indentation style.