Lacinia is well done, and, in combination with Clojure, a terrific labor-saving device.
In fact, Lacinia is so well-conceived that it makes GraphQL itself glow with labor-saving virtue. GraphQL is anyway splendidly low-impact for in-the-browser clients. In return, the burdens of GraphQL are borne by the server. Lacinia bears them. The chores left to your Clojure data service are considerably less onerous than GraphQL. Meanwhile, Lacinia seems to have no overbearing opinions. For example, you may analyze the whole breadth and depth of a Lacinia-parsed GraphQL query and optimize retrieval from some back-end database. But you need not. And Lacinia won't even notice the difference. Lowering the barrier to providing GraphQL services, Lacinia promotes an open and interoperable internet. Five gold stars. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
