-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
42 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# ClojureScript | ||
|
||
Official website: https://github.com/clojure/clojurescript | ||
|
||
## The answers | ||
|
||
1. What does the type system look like? **Dynamic** | ||
|
||
Derived from Clojure but with a few differences. Supports immutable, persistent | ||
collections. | ||
[[1]](https://github.com/clojure/clojurescript/wiki/Differences-from-Clojure#data-structures) | ||
|
||
2. Is there a stable version? **Sort of** | ||
|
||
1.8.40 is described as a "stable release" but it's nothing more than the latest | ||
cut from master. The numbering aligns with the Clojure version. | ||
|
||
3. Is it under active development? **Yes** | ||
|
||
The latest version was released in March 2016. The number of commits has | ||
dropped in recent months. | ||
[[2]](https://github.com/clojure/clojurescript/releases) | ||
[[3]](https://github.com/clojure/clojurescript/graphs/contributors) | ||
|
||
4. What is its [bus factor](https://en.wikipedia.org/wiki/Bus_factor)? **One** | ||
|
||
Development relies pretty heavily on its creator, | ||
[David Nolen](https://github.com/swannodette). | ||
[[4]](https://github.com/clojure/clojurescript/graphs/contributors) | ||
|
||
5. Does it support Dead Code Elimination? **Yes** | ||
|
||
Through Google's Closure library. | ||
[[5]](http://swannodette.github.io/2015/01/06/the-false-promise-of-javascript-microlibs/) | ||
|
||
6. How many libraries have been written or ported to it? | ||
7. What is the size of the runtime? | ||
8. Is it easy to integrate with the front-end toolchain (webpack, browserify, etc...)? | ||
9. Is it easy to integrate with JS libraries (ffi, definition file, etc...)? | ||
10. Is the language consistent? | ||
11. Is the output readable? | ||
12. How difficult is to hire a developer? |