1. 3

    I’m not trying to start an editor way in any way, but at this point: why not emacs? You’re losing the lightness of Vim by adding all these plugins, one of the best features of vim, in my opinion. I use evil-mode for almost everything in emacs, and I do wish it integrated better. Using vim simply for the universal conventions that come with it makes sense to me.

    1. 3

      What do you mean by lightness?

      You can have a fairly rich experience in vim without any added latency. Some plugins affect performance, but they’re swiftly removed from my bundle. Most of my plugins are language-specific and unintrusive, so they only load when the respective language is active in some buffer or I invoke them specifically.

      Forcing myself to use vim as just a text editor when it can be much more is unproductive.

      As for one why might prefer to use vim than emacs, it’s largely the same reason that I prefer vim over Sublime Text, or Atom, or Eclipse, or whatever. I feel more at home with vim, and I relate better to how the ecosystem operates than other options.

      1. 1

        I agree, although I still use vim. If you use vim, you should be using it as a text editor, and not an IDE. If you want an IDE as your editor, then use emacs. If you want an IDE and vim, then take advantage of more versatile tools like your shell and language REPL or something.

        1. 8

          Or you know, the guy can use what he wants for what he wants. If he wants to try and turn vim into an IDE, who are we to tell him that he is wrong?

          To call the OP’s setup an IDE is a bit of a stretch regardless. And OP does mention moving to the REPL in another terminal “you must launch a Clojure REPL manually in another terminal thought”.

        1. 3

          Connect as any user, not just root, and sudo as needed

          This is quite a big feature which was preventing me from using other similar tools like Sprinkle (with Capistrano [Ruby]). Sometimes within these large “enterprisey” companies, you aren’t actually in the sudoers file. Requiring sudo all the time was a silly choice.

          1. 3

            Makes me jealous. I would love to build tooling like this, never worked for an employer that valued these things enough to let me do it.

            1. 2

              If it’s worth it, find the time. You may just inspire the ones making the decisions of what is ‘value’.

              1. 1

                There is always a balance to made between investing in infrastructure and banging out the minimal set of things to take you where you need to be next. It’s also very difficult to know what is the best move to make at any given time. In my experience some organizations more heavily favor infrastructure investment (e.g. github) while others do not. If you’re in an organization that is biased against infra development then you’re going to need to work hard to sell your ideas…

                1. 1

                  Infrastructure at my company isn’t the highest on the list of things to do. It’s sad to say we’ve had to almost fight to get time to maintain infrastructure. Maybe it’s because I’m young and dumb but I’m working on tooling exactly like this post funnily enough. It needs to be done but it’s not exactly “my task for the week”. If anything I’ll write it off as a cost of making my future tasks easier to solve.

                  I’m not exactly “selling” the idea, it seems I’m doing it for free.

            1. 2

              Funny seeing a post by Beau on here already! Small world. I think I’m correct in saying that Beau is hacking here in either Ruby or Clojure? I feel exceedingly happy as a hacker more often now that our prototyping no longer resides in static languages (ala Java).