Good question.
Before I answer it directly, please allow me to share some history about
GraphQL.
Back 2016, I felt the pain of maintaining different versions of RESTful api
for both web application and mobile application. I believed GraphQL was the
answer. So I tried to look around, there was no
Glad to see this separation.
Also I just wanted to chime in and say that I greatly appreciate the work
you've done with Spec. It's been a great help to me.
On Thursday, April 27, 2017 at 8:20:16 AM UTC-7, Alex Miller wrote:
>
> Clojure 1.9.0-alpha16 is now available.
>
> [...snip...]
>
Also
Clojure 1.9.0-alpha16 is now available.
Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.9.0-alpha16
- Leiningen: [org.clojure/clojure "1.9.0-alpha16"]
1.9.0-alpha16 includes the following changes since 1.9.0-alpha15:
- The namespaces clojure.spec, clojure.spec.gen, c
On Thursday, April 27, 2017 at 3:05:26 AM UTC-5, Tamas Herman wrote:
>
> What problems would it pose if the alpha status would be reflected in the
> version number of org.clojure/spec,
> just like it is the case with org.clojure/clojure rightnow, which is
> 1.9.0-alpha15?
>
At some future point
What problems would it pose if the alpha status would be reflected in the
version number of org.clojure/spec,
just like it is the case with org.clojure/clojure rightnow, which is
1.9.0-alpha15?
I've seen the Spec-ulation Keynote from Rich and this step feels like an
experiment
to try out the id
