blog:enterprise_clojure_is_not_a_bad_phrase
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
blog:enterprise_clojure_is_not_a_bad_phrase [2017/05/25 16:13] djo |
blog:enterprise_clojure_is_not_a_bad_phrase [2017/05/25 16:16] djo removed |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== 'Enterprise Clojure' and Specs ===== | + | ====== 'Enterprise Clojure' and Specs ====== |
| Over the past two years I have been using Clojure to deliver an Extract-Transform-Load (ETL) pipeline. During this time, I have spoken with a number of other developers who use Clojure to deliver larger-scale applications, and among some of these developers a consensus has arisen: "Clojure is too hard to use at larger scales." | Over the past two years I have been using Clojure to deliver an Extract-Transform-Load (ETL) pipeline. During this time, I have spoken with a number of other developers who use Clojure to deliver larger-scale applications, and among some of these developers a consensus has arisen: "Clojure is too hard to use at larger scales." | ||
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
