Re: Liberator with ring-cors

Kenny, Take a look at this repo: https://github.com/open-company/open-company-api We're using Liberator with: [jumblerg/ring.middleware.cors "1.0.1"] Works fine... The middleware handles the CORs portion of the response: https://github.com/open-company/open-company-api/blob/mainline/src/open_c

Re: recombining results from clojure.data/diff

On Thursday, October 15, 2015 at 5:26:01 PM UTC-4, JvJ wrote: > > I just discovered clojure.data/diff, and it's great. However, I'm not > sure how to recombine the results to get back the original. > > For instance, if (diff a b) = c, then how can I combine b and c to get > back to a? > > Merge

Re: New version of core.async?

Alex, +1 Glad to hear you're going to get a new core.async out. That's huge. In particular the old tools.analyzer.jvm dependency seems to be causing lots of problems using core.async in bigger projects that use other macro powered libraries. Cheers, Sean On Thursday, August 6, 2015 at 7:43:

Re: [ANN] Nginx-Clojure v0.4.0 Release!

Congratulations on the 0.4.0 release Yuexiang! Nginx-Clojure is by far my preferred way to deploy Clojure web apps. FWIW, Re: #14, if anyone is interested in using Nginx-Clojure with the mainline version (1.9.2) rather than the latest stable (1.8.0) that's in the Nginx-Clojure binary, I built 1

Re: Clojure needs a web framework with more momentum

I thought about it and all that came to my mind that there simply won't be an upgrade path. Once you generated your code / templates / whatever you are done and up to yourself. Having a supported upgrade path might be 1. to much for one or two persons to handle 2. Incompatible to the "generate"

Re: Clojure needs a web framework with more momentum

On Monday, May 4, 2015 at 4:41:02 AM UTC-4, Sven Richter wrote: All in all this is basically the direction I want to go with closp and > closp-crud. The intention is not to have a webframework, but to automatize > steps that need to be done manually otherwise. > One potential problem with thi

[ANN] POSThere.io 1.0.0

POSThere.io ( http://posthere.io ) is a simple free service for developers to help debug API calls and web hooks. When your code is POSTing to someone else’s code… or they'll be POSTing to you, it can be hard to iterate, debug and validate your code. POSThere.io let's you see what is POSTed (or

Re: [ANN] cuerdas 0.1.0: A string manipulation library for clojure and clojurescript.

Very nice work. I'll be using this! Also, I agree with Noam that there's a fairly common expectation of blank? that started in the Ruby world. Here's my suggestion for what it's worth: blank? - true iff "" or nil empty? - true iff "", false if nil whitespace? true iff "" or only white space, fa

Re: Leiningen setup for modifying a library the project is depending on

You also should have a look at lein-git-deps - https://github.com/tobyhede/lein-git-deps It's not quite as seamless to drop in as lein "checkouts", especially if you are working alone. But if you're on a team, it has the benefit of being explicitly baked into your project.clj so you know all te

Re: Proposing a new Clojure documentation system (in Clojure)

> > So it would be nice if people who are knowledgeable about other doc > systems could contribute to it. From what I see, that may involve Tim for > Emacs, Sean for reStructured, and Daniel for docco, for example? > I took the liberty of fleshing out the document

Re: Proposing a new Clojure documentation system (in Clojure)

Valentin, et al, I'm a little late to the thread here, but I'm the author of lein-sphinx which you mentioned in your (well thought out) post so I thought I'd weigh in here. I agree with a lot of what you wrote in your proposal, and for many projects (not all of them, but many) there is an impo

Re: [ANN] Clojure 1.6.0-RC3

I get the following warning when using 1.6.0-RC3 WARNING: record? already refers to: #'clojure.core/record? in namespace: clojure.core.logic, being replaced by: #'clojure.core.logic/record? when requiring [clojure.core.logic :refer (run* membero distincto ==)] Doesn't happen with 1.5.1. Exclud

Re: A question for TDD practitioners

I'm a bit more TDD inclined than the average Clojurian (having come over most recently from Ruby/Rails) and I have to say speed is king in TDD. I agree that source maps are life savers when you need to debug an issue in browser, but I don't really see how they'd be all that useful in the average

Re: Storing data on web server with Clojure

Keep in mind that the Heroku file system is a little "funky". Writing things there is not like you're used to with your local system or with a VPS or dedicated server. It's ephemeral and those files will disappear during certain events. I agree with the other Sean, that if the data is small and

Re: Do web apps need Clojure?

I'm a "Rails guy" who now uses Clojure for all new web development, so don't take what I'm about to say as disagreeing with Justin. As someone with a foot firmly in both worlds, a couple of Justin's points aren't really marks in Clojure's favor, at least compared to Ruby/Rails (I can't say as

[ANN] lein-sphinx - Generate documentation from reStructuredText using Sphinx

I'm happy to announce, just in time for all the great documentation that will be written at Clojure/conj, the initial release of the lein-sphinx plugin. https://github.com/SnootyMonkey/lein-sphinx lein-sphinx makes it easy to configure the build(s) of your Sphinx [1] documentation in your Le

Re: (Clojure-related book) Seven Concurrency Models in Seven Weeks

According to page 11 of this: http://media.pragprog.com/titles/pb7con/intro.pdf They are: 1. Threads & Locks (old school) 2. Actors (Erlang and its clones) 3. Functional Programming (no mutable state) 4. Separate State and Identity (Clojure) 5. Data Parallelism (something about GPU's) 6. Lambda

Sharing result of macro's calculation with the body

Hello, If a macro calculates something and wants to make that result available to the body, what's the right way to do that? So far I've tried these ways which don't work (this is not really my macro, it's just a simplified example to demonstrate the issue): 1) lexical scope doesn't work, the