|
|
|
|
|
by kamaal
5172 days ago
|
|
According to me tools have practically zero chances of survival without communities rallying behind them. This looks like such a cool idea. I think their primary concern must be to release a basic thing out first and then iterate over it. This way they will get both contributions and the product going. Decide what your design goals are, define what code and quality goes in and out of your repo. Build something basic, release it and then iterate. Contributions and donations will follow. But if you are expecting mass adoption for a tool designed primarily for Clojure then, Clojure itself is in low adoption stage now. On top of that people who use clojure wanting to use will be fewer(Emacs + Slime really works well). So the initial payment model with only Clojure support may not bring them much money. This definitely has to be a platform like Emacs. And then the money can come from upgrades, major revisions. Also it would have been nice if language used to extend this was Clojure itself. We desperately need some modern GUI candy on an Emacs like editor which can be extensible by Lisp. |
|