Fork me on GitHub
Alex Miller (Clojure team)16:12:27

I'm currently trying to finalize the "State of Clojure" survey. I'm trying to add something less free-form to let people indicate priority of feature work areas. Looking for some feedback.

Alex Miller (Clojure team)16:12:39

Currently I have a question "Which area of Clojure could use more attention?"

Alex Miller (Clojure team)16:12:05

with choices like: Startup time, Performance, AOT, Error msgs, docs, namespaces, portability

Alex Miller (Clojure team)16:12:32

Is that a good question? What choices should be added?

Alex Miller (Clojure team)16:12:12

I do not intend to add choices for things that people routinely suggest that we do not intend to work on (TCO, "stack traces", static typing, new runtimes, clj in clj, pattern matching) or tooling-related things (like debuggers). I'm trying to make this area of the survey actually produce actionable data.


@alexmiller: validation, compilation knobs? simple_smile


validation = less GIGO, more input validation


which is different from asking for better error messages

Alex Miller (Clojure team)16:12:42

does "error messages" cover that or is it more?


error messages are after failure, validation is before


and potentially at compile time


dunno if that's something people want, it's definitely something that I would pick thugh

Alex Miller (Clojure team)16:12:31

so more compile time input validation


not necessarily just compile time

Alex Miller (Clojure team)16:12:33

is compilation knobs something else? or is that more control over stuff like direct linking?


and compilation knobs = ability to turn on/off inlining, prim-invoke etc just like we have for DL, metadata elision

Alex Miller (Clojure team)16:12:05

you have metadata elision now


yes, I know


"just like we have metadata elision"


natural languages and their weird precedence rules


@alexmiller: is the same question going to be in state of clojurescript survey?