# From Twitter: how do we sell Clojure?

**URL:** https://clojureverse.org/t/from-twitter-how-do-we-sell-clojure/1184
**Category:** General Questions
**Created:** [December 13, 2017, 10:43am UTC](https://clojureverse.org/t/from-twitter-how-do-we-sell-clojure/1184 "2017-12-13T10:43:21Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![mikeb](https://clojureverse.org/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@mikeb](https://clojureverse.org/u/mikeb)
#### Post date: [December 13, 2017, 4:56pm UTC](https://clojureverse.org/t/from-twitter-how-do-we-sell-clojure/1184/5 "2017-12-13T16:56:40Z")

</div>

I believe the brightest path forward is community based CLJS distribution/community, called something like “CLJS Stack” that breaks(not a fork and still use clojurescript) from the core clojure team and focuses on the javascript community. I would minimizes/hide the jvm as much as possible and operate with a community culture like that of the rust, reasonml or elm communities. It could include

- node based cli called cljs where startup time is important (lein/boot need to go)
- ‎shadow-cljs is the compiler
- ‎cljs libs deployed to npm or somewhere js friendly.
- ‎common way of running unit tests in browser and in node.
- ‎vscode primary editor (emacs needs to be discouraged)
- ‎debugging with chrome devtools
- [docs.cljs.io](http://docs.cljs.io), (api docs cljs only) [how.cljs.io](http://how.cljs.io) (task based cljs only)
- forum for cljs questions (no jvm clojure stuff) so we don’t confuse users
- workflow to handle css/design assets (for designers)
- community managed & supported libs for primary/common needs
- ‎guidance for common app types (cli/jsapp/api/serverless/etc)
- easy way to support financially (patreon or open collective)

---

_[View the full topic](https://clojureverse.org/t/from-twitter-how-do-we-sell-clojure/1184)._