Re: Reactive programming

2014-03-22 21:10 GMT+01:00 Marc Weber <marco-oweber@gmx.de>:

Excerpts from Gautier DI FOLCO's message of Sat Mar 22 19:07:51 +0000 2014:

> I really mean reactive programming: when some variables are changed
> expressions which dependent on them are recomputed.

Reactive tools I know about:
- ruby guard https://github.com/guard/guard
Thus if you "write" you can run actions
Eg it can reload files in browsers, regenerate tags and whatnot.

vim-addon-actions allows to bind actions such as "compile file" to buf
write events

Other than such "hooks" Vim is not reactive - more event based (which
can be used to achieve the same, but you know that).

> My final goal is to have an UI like Light Table

Then use Light Table

The bigger the system you're working on the less likely you want the
editor to "redo" whenever you hit some chars. It heavily depends on what
you do.

Thus to keep the story short: just because you insert a space in
coreutils source code you don't want anything to trigger rebuilding your
linux system (would take too long). Thus it does make sense to
concentrate on your task and judge yourself when its worth rebuilding
something. (That's what I found out).

neovim.org is a project by Tarruda fund by bountysource.
If you come up with a nice decsription about what you exactly mean
you can try talking to him or vim-dev mailinglist.

Until that happens think about when you want to be reactive, maybe tools
like the ones mentioned above can help you come close.

Marc Weber

Thank you!
What would have I done without you?
If I choose to improve ViM it's because it fills 95% of my needs.
Have I to stay with this 5% of unsatisfied needs? Clearly not, moreover I thought that ViM was made by developpers, for developpers. I'm a developper, it's legit for me to develop it.
No one have forced you to answer to my messages, so, if your only aim is to bring almost no new data and insult people, don't answer.

I'm not a new user of Vim, but I think if it had been, I would have changed editor.
I saw ViM be improved every year and I don't see why Vim should confine itself to reinvent the wheel 10 years later while other editors have had introduce one good idea easily backportable.
You can stay in your cavern, but don't force others to stay with you because you're afraid by the sunlight.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.