This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-22
Channels
- # aws (1)
- # bangalore-clj (3)
- # beginners (103)
- # boot (15)
- # cider (29)
- # cljs-dev (17)
- # cljsrn (43)
- # clojure (156)
- # clojure-gamedev (2)
- # clojure-italy (11)
- # clojure-spec (55)
- # clojure-uk (4)
- # clojurescript (76)
- # data-science (2)
- # datomic (7)
- # defnpodcast (2)
- # emacs (4)
- # leiningen (2)
- # luminus (3)
- # off-topic (11)
- # parinfer (3)
- # pedestal (1)
- # quil (1)
- # re-frame (3)
- # reagent (2)
- # ring-swagger (1)
- # timbre (3)
- # unrepl (10)
- # untangled (1)
- # vim (3)
- # yada (1)
@cgrand my concern with smart clients is that it potentially increases the work significantly of all clients, causing an X doesn't work with Y, but Z does scenario - so you copy and paste code from vim into unravel to take advantage of some hub feature.
Other use case came up yesterday: - One person has docker instances and wanted to be able to refresh namespaces within it based on the activity in the local repl/editor (you change the buffer, it refreshes the remote repl) - Malcom wanted to be able to reflect changes from a REPL to the actual files on the filesystem - One other person had the same idea and that remembered the Logo IDE was doing that
I think Logo is this one: https://en.m.wikipedia.org/wiki/Logo_(programming_language)
Don't remember the person but basically the idea would be to change things in the repl and keep track/diff this with the file you are starting with. When you want to persist the changes you call a REPL function that consolidates and writes to disk
@U0C8489U6 the Logo idea came from Panu, which also had the docker instance refresh usecase.
To be sure I get it correctly, is it "refresh 1 docker instance" or "refresh N docker instances"? and this occur in addition to the local repl? So basically syncing several JVMs (or JavaScript VMs)?
Sorry for the sparse reporting but the post conference was intense 😀