33 karma · joined October 1, 2013
I've got the `(add-to-list 'load-path "~/.emacs.d/lisp/")` pretty early in the file. You can put the `(require `ido) (setq ido-enable-flex-matching t) (setq ido-everywhere t) (ido-mode 1)` where you like. Basically, you just need the lines in your .emacs file - if you add the reference prior to creating the directory and populating it, you'll get an error, but nothing will break. Add the directory and do a `M-x eval-buffer` and it'll pick it up without restarting emacs. Or just restart emacs. Hope this helps. Someone will tell you a better way.
Regarding organization, I don't have much of a system, other than the filesystem under ~/org with a handful of directories. Works just fine for me. It's more about not-caring than caring, regarding organization of information. We really shouldn't have to organize this stuff. Emacs + org-mode allows me to not care. I love that.
Where do you think our approach will add overhead to your development? We'd love to know so that we can either explain better or get a better product match for you. With Fugue, you get a Conductor that continually monitors and conforms the environment to your declarations - we think that has a lot of value for operating your environment as opposed to just creating it.
- Josh
It will indeed! And with a compiled language so you can get meaningful errors, etc. before spinning up resources that cost $.
- Josh
Thanks for the comments and well-wishes! We chose to use some new terms to not overload existing ones where we are introducing new concepts (Conductor, Performers, etc.). The analogues to music conceptually were so strong they seemed the right way to go. We will have lots more in the way of howto's, screen recordings, etc. in the coming weeks as we recover from launching our beta at re:Invent. Sign up for the beta and we'll send out bits with examples and runnable code in <15 mins.
- Josh
Disclosure: I am a founder and the CEO of Luminal.
In a distributed, and therefore often largely stateless system at the instance level, the system boundary is now outside the individual instance. The performer (a series of instances over time in Fugue) is roughly analogous to a process on an individual computer. Truth and trust are maintained by knowing and controlling the state of the instances themselves with Fugue. Think of the Conductor as analogous to the kernel in a traditional OS, where providing processes CPU time and resources is a regular course of business.
As for unnecessary work, we've found that maintaining systems in place, with all the failure, complexity and configuration drift that's inevitable is much more expensive than using some of the excess capacity of a given performer. Most systems target 70% or so utilization - we use some of that excess to lifecycle.
I hope this answers the question and we're really excited to get feedback on what we're doing so it's relevant to your work.