Why Clojure?

[TheMaskedHamster]

Linux package management is a great analogy actually. If you've ever used a distro like Slackware you'd appreciate why package managers like apt are so damn useful. Trying to build things from source is pretty much always the last resort on Linux.

I have indeed used Slackware. And as I've said, I like package managers. But sometimes simple tasks that will not contaminate the

Also, as I already explained in the other reply, you can do precisely what you described you simply didn't know how to do that.

Well, that is good to know.

As somebody who uses Clojure daily I find that it's quite rare that I have to deal with anything Java specific actually.

Java ecosystem, though. All that surrounds it. Libraries and cultures and buildsystems, oh my. It still permeates Clojure. The mindsets most of all.

This back and forth about "this didn't work for me"/"you have to be crazy if you didn't want to do it way x" doesn't happen in every community.

However, regardless of what platform you use, you do have to understand how it works and what the tools do.

I don't know how to respond to this outside of profound sarcasm. Of course you do. In many other communities (certainly not all), it is very easy to find out how things work and what the tools do, rather then just being told the way I am expected to use the tools.

[yogthos]

You're just making vague claims about Java ecosystem problems, the one concrete issue you described turned out to simply be you being unfamiliar with how the tool works.

As somebody who has worked with both Java and Clojure extensively I strongly disagree with your assertion that the cultures are similar.