Clojure Web Infrastructure
glenstampoultzis.net
glenstampoultzis.net
This is an important point about Clojure - the culture seems to be leaning towards multiple small libraries, rather than whole frameworks or packages.
Which is actually kind of neat, since a properly written Clojure library is much more composeable than libraries in most other languages.
Similarly there isn't as much of a need to have a monolithic stack like Ruby has, because Ruby's style tends to step on other's work a bit leading to preferring a all-in-one style for reliability.
I understand that Clojure is still young and that it's ecosystem is still evolving at a fast pace, and I understand why the changes being made are largely improvements, but for my particular circumstances it's a large headache.
EDIT: Here's a hint for people want to get a Clojure environment going but can't use one of the package managers for some reason or other: You can visit clojars.org and download all of the jars that you need. This was, you don't need a build system on you development machine. You still have to figure out what the dependencies are manually, but you aren't stuck if you can't get Leiningen or Maven working.
I think it's a cultural difference within the Windows development community. I've made maybe two bug reports to Microsoft related to .NET or SQLServer in the past 8 years. Everything else was either already reported and being fixed in the next 2-3 years or was reported and written off as "you are on your own - we're not fixing it". I've had similar experiences with big proprietary Windows frameworks like DevExpress. Unfortunately at this point I don't think it's changing because it's what everyone expects.
After finding the nth response like this it becomes apparent that it's easier to just find a work around and complain rather than continue to bash your head into the wall.
Hopefully Windows users will learn to contribute and report bugs in community driven development someday...
That's not really fair, there are some great teams in MS. My impression is that the difficulty of communicating with anyone useful correlates pretty well with how enterprisey the product is.
I ran into problems where lein.bat didn't work in powershell or msys. This is commonly the case so I didn't think it warranted any bug reports. It did take some additional effort but it was similar to the effort required to get just about anything working in clojure.
For the record my take is this is a Microsoft problem. They need a packaging system that works and is built with all the crazy native windows development quirks in mind. See http://coapp.org/
Alternatively, if you're having trouble with the lein.bat, you could try lein.ps1. (https://gist.github.com/395038) I believe that lein.sh is meant to work pretty well on cygwin now, though.
I can't stress how much more productive you'll be. And we're a shop selling Windows software to Banks and bigger corporations.
clj-record shows promise but is still rather rough around the edges. I'm hoping to contribute some patches.
I'm still trying to get to grips with Leiningen: one thing I haven't figured out is what the best way to use local jar files for Java libs. Also, using locally modified versions of libraries which are already in the leiningen system doesn't seem an intended use case.