This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-01
Channels
- # admin-announcements (3)
- # arachne (6)
- # boot (17)
- # cider (51)
- # cljs-edn (19)
- # cljsjs (1)
- # clojure (22)
- # clojure-russia (154)
- # clojurebridge (5)
- # clojurescript (20)
- # cursive (1)
- # emacs (2)
- # ldnclj (1)
- # liberator (1)
- # mount (1)
- # om (44)
- # onyx (6)
- # ring-swagger (4)
- # rum (30)
- # slack-help (8)
- # untangled (40)
added a planck example: https://github.com/shaunlebron/standardized-cljs/tree/master/examples/planck @mfikes
i feel like my visibility of the problem-space is getting better, not convinced of any solution yet
just a proposal, let me know how that jives with your direction with planck
i still have to think about boot, the last example left
@shaunlebron: Yep. Looking good. (As an aside, your mention of npm reminded me of an idea that Planck could also conceivably support :module-type :commonjs
by shelling out to Closure. In which case, Planck would continue to just follow the existing config standards and not innovate there.)
@mfikes: if you could shell out to closure for that, would be interesting to see if it could become a full build system, haha
Yes. I was pondering that the other day. Planck already uses itself to AOT its own macros. http://blog.fikesfarm.com/posts/2016-02-03-planck-macros-aot.html It is 1 step away from being a build system. (But, there’s probably a lot more to a full-fledged build system.) You could almost get philosophical about the intermixing of runtime / compile time / read time (Paul Graham’s item 9). In short, since Planck doesn’t need to AOT for deployment to the web, it currently enjoys freely blurring the distinction, even having eval http://blog.fikesfarm.com/posts/2016-01-22-clojurescript-eval.html. Part of my philosophical view is that ClojureScript was heavily affected and shaped by its need to AOT for a remote JS environment, one that I’ve never targeted. (I’ve only used ClojureScript outside of the web.)
that’s really interesting
This is an interesting take on it, from someone we respect: http://blog.fogus.me/2011/07/29/compiling-clojure-to-javascript-pt-2-why-no-eval/
glad that planck is there to see that distinction
@mfikes: just re-read those articles a few times. very cool stuff. i feel like i understand Lisp a little better now
i kinda missed all that stuff because my experience with Lisp has been in this constrained browser environment
might be a dumb question, but is clojure self-hosted?
because it has eval?
Yeah, I’ve been meaning to write a “philosophical” post discussing the two extremes that ClojureScript now affords us. Will scratch that together.
I think to be self-hosted, you need to be able to compile yourself. But but that’s an interesting question, given “hosted” languages like Clojure and ClojureScript.
i get lost in the layers of it all when thinking about it