This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
quick question, can I license some code under the MIT if it contains some copy-pasted function taken from an EPL-licensed project?
I never liked "immutable data structures", which may let you think mutable data structures are more natural. How about "value - oriented" or "program with values"?
Perhaps "Persistent data structures" or "fast persistent data structures" would be better?
Also, if you're going to use the "simple made easy" phrase in such a prominent / graphical fashion, you should capitalize each word.
Also, I'd use a lighter font for the word "Clojure", and if you want to keep the cheeky touch from the homepage, italicize the "j"
I'm on my iPad so I can't tell for sure, but is the blue of "Clojure" different from the blue of the name? I'd make them the same. And you could make the "simple made easy" the same green as the logo.
Also, will the audience be familiar with the distinction between simple and easy ?
as it "just" a poster I don't mind leaving a few things open... that give us a starting point for discussion after all
looks like "Designed for Concurrency", "Lisp", and "Multiple Platforms" seem to be the major points from that page
some of the best Clojure I wrote was building a test suite for a Java Swing application in 2010 before ClojureScript was even announced
I don't mean at all to take the fun out of it, but... it really depends on what the objective is IMHO. If you want this poster to be Clojure's elevator pitch, you need to express some part of Clojure's value proposition in a way that is clear, succint, credible, compelling, and intriguing (and you don't need to do justice to its actual value proposition). If you want it to be the rallying point of Clojure aficionados, then it makes sense to collect all the things clojure user love best
a poster in the halls of Clojure/conj should look wildly different than one hanging in your office at a Java shop you're trying to pitch Clojure to
Personally, what I love most with Clojure is that it makes programming so natural, so much closer to what programming would be in a perfect world; notably, it does so by making a whole lot of superfluous concerns and tradeoffs just go away (instead of providing more sophisticated way of addressing them. Yes, Scala, I'm talking about you).
to me, the fact that there is less boilerplate is the least important part of it; but again, depending on your target, it may be a good argument
@val_waeselynck I understand... and that is why I'm asking here... get a second opinion
I would not mention less boilerplate. I would not want to see Clojure lowering itself to the silly level of "Look, no curly braces and no semicolons!"