This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-31
Channels
- # aws-lambda (4)
- # beginners (152)
- # boot (19)
- # cider (45)
- # cljs-dev (14)
- # clojure (54)
- # clojure-dev (33)
- # clojure-greece (11)
- # clojure-italy (4)
- # clojure-nl (8)
- # clojure-norway (2)
- # clojure-russia (6)
- # clojure-sg (1)
- # clojure-spec (1)
- # clojure-uk (40)
- # clojure-ukraine (5)
- # clojurescript (40)
- # community-development (13)
- # component (8)
- # core-async (3)
- # cursive (25)
- # data-science (11)
- # datomic (13)
- # duct (1)
- # emacs (2)
- # events (16)
- # figwheel (3)
- # fulcro (53)
- # graphql (2)
- # jobs (5)
- # jobs-rus (1)
- # juxt (10)
- # leiningen (4)
- # off-topic (82)
- # other-languages (5)
- # portkey (3)
- # protorepl (13)
- # re-frame (22)
- # reagent (15)
- # ring-swagger (4)
- # shadow-cljs (69)
- # spacemacs (7)
- # specter (16)
- # sql (13)
- # vim (5)
- # yada (2)
I'm trying to decide about language plugins for neovim, and if they are a good idea. Traditionally I think non-viml plugins have struggled to gain traction. A lot of plugins in fact tout it as a feature (e.g. Airline)
Managing dependencies for some of these languages is near impossible in a traditional way, and involves maintaining source copies yourself.
Have you done anything with lua? I haven't personally. The majority of the vim plugins I wrote used Python which worked well enough to achieve the goals I was pursuing at the time. It has been years at this point since I have written anything more than the odd function for vim. Does the promise of first class lua treatment influence the potential lack of traction for non viml based plugins?