This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-29
Channels
- # aleph (3)
- # announcements (16)
- # beginners (85)
- # calva (2)
- # cider (13)
- # clj-kondo (84)
- # cljdoc (3)
- # clojure (109)
- # clojure-belgium (1)
- # clojure-china (39)
- # clojure-europe (4)
- # clojure-france (1)
- # clojure-italy (70)
- # clojure-nl (8)
- # clojure-spec (8)
- # clojure-uk (53)
- # clojuredesign-podcast (14)
- # clojurescript (43)
- # cursive (25)
- # data-science (1)
- # datomic (4)
- # emacs (10)
- # figwheel (4)
- # garden (4)
- # graphql (5)
- # jackdaw (10)
- # jobs (5)
- # jobs-discuss (5)
- # lambdaisland (2)
- # leiningen (3)
- # luminus (7)
- # off-topic (32)
- # pathom (11)
- # pedestal (2)
- # planck (15)
- # re-frame (12)
- # reagent (4)
- # remote-jobs (2)
- # shadow-cljs (51)
- # sql (29)
- # tools-deps (47)
suitable provides "IntelliSense" for ClojureScript / JavaScript interop by using the live runtime for method / property enumeration. Figwheel and CIDER are supported right now. https://github.com/rksm/clj-suitable
This is super! I have been thinking about it for such a long time now, thanks for the effort!
Would love to see the same thing for shadow-cljs as well 🙂 Good job @U08LZDL1H
Thank you 🙂 Haven't worked with shadow-cljs yet but will take a look.
@U4BEW7F61 No, this should run in other repls as well. I tested it on nashorn and with weasel. All it needs for use with cider is that the cider-completion and piggieback middlewares are there - which is the default.
Would it work if I do cider-connect-cljs
?
We published a blog post about one specific but important tactic I used when writing libpython-clj in order to allow python to call clojure functions. I don't think this is necessary knowledge to use panthera or libpython-clj but it is a key piece to building a new binding to a C system elsewhere and just a good general piece of knowledge about how certain things work in the C world: http://techascent.com/blog/functions-across-languages.html Also, libpython-clj, the underlying tech stack, and Alan Marazzi's Panthera all have new versions out. Enjoy 🙂
I dug into Reagent Components and wrote about my journey to understanding what happens to them by the time they get to React https://betweentwoparens.com/what-the-reagent-component
Input is very welcome :hugging_face:
> They are not a formal syntax in the language wich you can just look up.
it's nice, thanks! I have little JS background and I can't see where you explain why things are being done like that instead of in the traditional 'pseudoclassical instantiation pattern'
That’s a good point.
The reason I did not specifically address that is because my answer would be based on inference rather than providing the actual reason as to why the Reagent team went the route they did.
I actually went so far as to replace the create-class
implementation with the traditional pseudoclassical instantiation pattern
I specified in the blog post and Reagent seemed to continue to work as is and the tests continued to pass 🤷
So based on this the best I can do is say: maybe there was/is a technical reason (google closure compiler related?)? or perhaps their implementation just worked so they went with it?
Either way, I will address this in the footnotes.