Right, just like "altruism" is also rooted in self-interest. It turns out that people are motivated by all kinds of things.
1,307 karma · joined April 14, 2012
Right, just like "altruism" is also rooted in self-interest. It turns out that people are motivated by all kinds of things.
Try codi.vim for REPL-like eval:
Shipping Lua as a first-class alternative to VimL also happens to be the primary goal for Neovim in 2017.
However...
> stuff like the following makes it hard for me to resist switching.
I don't think one should "resist". IDEs (VS code is an IDE, at this point) are very powerful. I really wish vim-modes would go away; I would like to see Neovim embedded in VS code and friends, instead. By "embed" I mean: nvim is the text editor, it does everything; it lives in the "document" area of the IDE; and you can bind nvim keys to IDE functions/commands (such as "Open Type...").
Neovim is designed to be hosted (embedded). Embedding Neovim in a IDE (platform) allows Neovim to be the editor while exposing the IDE as "the platform".
It's also a guiding principle of Neovim to not dictate what applications are built with it, so yes, you can leverage its API as a platform. But that's not the singular purpose.
> I guess what I mean is that vim should be left as vim. There are superior platforms that implement the same interface,
There are no applications that implement Vim (except Neovim, which passes Vim's test suite).
See the updated FAQ[1]. We are punting on the VimL-to-Lua translator. We think it will be more valuable to instead ship Lua as a first-class alternative to VimL.
> (suffering from code rot and filled with preprocessor declarations for dead platforms) in Lua w/o degrading performance too much
eval.c is being refactored in PR 5119[2].
The Neovim patch[3] to add built-in lua scripting will support both luajit and PUC lua.
I also updated the FAQ[4] to avoid confusion.
1: https://github.com/neovim/lua-client
2: https://travis-ci.org/neovim/neovim/jobs/162545247
So absence of scarcity will totally be a thing if everything just goes according to plan. Got it.
That's an incomplete statement, because it doesn't quantify the effect. Will the effect be zero, or will BI be priced-in (higher prices, lower present-value of BI)?
US college tuition and housing prices increased dramatically, because of decreased consumer price discrimination driven by low-barrier loans.
If [over]population is a factor, then "post-scarcity" is fiction.
This makes me think BI advocates are quietly assuming constraints such as "we'll discourage reproduction somehow"--while constantly mentioning how BI will be free of constraints.
> A touch of generics done properly, a bit of reflection,
Dapper avoids reflection, its performance is very close to a hard-coded SqlCommand.
> Cloud features and APIs should be a commodity not a differentiator
> ...
> We would prefer to be an insignificant customer in a giant cloud.
C++ is a rather low bar.
> It's a just a matter of time ...
That sets the upper limit to infinity, so it's a non-statement.
> Because it's easier to learn It's easier to write, because there are no syntax or compiler errors.
AST-constrained editing (e.g. lamdu[1]) will be very useful. But the lowest-common denominator cannot be "overtaken". That is why stdio is a binary stream, webapps are compiled to javascript, and programming is represented as text. Any advanced programming language that can't be represented and manipulated by ubiquitous tools will lose to one that does, so text will never--yes, never--be replaced as the common vernacular, for better or worse.
To paraphrase Stephen Kell[2], Smalltalk lost because for whatever reason the people who hadn't yet "seen the light" continued to communicate and interoperate with each other.
2: https://www.cl.cam.ac.uk/~srk31/research/papers/kell13operat...
Neovim also does not depend on ncurses. Vim optionally links to it for termcap/terminfo access.
$ ldd $(which nvim)
linux-vdso.so.1 => (0x00007fff75590000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f821b0ea000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f821aecc000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f821acc7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f821a9c1000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f821a7be000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f821a3f8000)
/lib64/ld-linux-x86-64.so.2 (0x00007f821b301000)This was directly addressed in a 2011 talk[1] by a director at Netflix:
> Competition drives cost down
> [...]
> We would prefer to be an insignificant customer in a giant cloud.
[1] https://justinmk.github.io/2016/03/17/selfish-cooperation.ht...
nodejs is built on libuv[1], which uses IOCP on Windows (and epoll, kqueue, etc. on other platforms). What's non-optimal about it?
> Dumb Jump uses The Silver Searcher ag (and falls back to grep) ... [and] a set of regular expressions
If you're going to install ag, you might as well install universal-ctags[1], a revival of ctags with many improved and new parsers. It allowed me to discard my C and javascript ctags config entirely.
Combined with gutentags[2] you have a "just works" and "Less Dumb" setup.
It's also quite alarming to reach a level of proficiency where you can make non-trivial edits without looking at what you're editing, and know that the edits are correct. Again, this avoids context-switches.
That's why Vim is so focused on precision ("do exactly this") rather than DWIM ("Do What I Mean [usually]": the emacs/IDE approach).
Certainly whether the ramp-up cost is worth the "payoff" is debatable, but for me, editing text became so irritating that my initial experiments with Vim were driven from pure exhaustion after years of blub-craft.
If your project has its own .git directory, no, it won't add to ~/.git.
*
git tracks modifications to your dotfiles. And on the rare occasion that you need to add a new file, just force-add it: git add -f ~/.foorc
If you need a script to "install" your dotfiles, you're doing it wrong.