Thoughts on Clojure Hacking

[kmfrk]

I'm sorry that this might be the wrong place to ask, but why is sbochins's name coloured green?

Is it because I've upvoted him a lot - or he me?

How does it look for other people?

[mcav]

It's a new account. (think "Oh, he's green at that")

[sbochins]

Have been a long time reader, just signed up a few days ago. Was wondering what the green meant at first too.

[shadowpwner]

Should we be drawing more or less attention to newcomers? The green is more obvious than the default gray.

[choffstein]

Looks green to me

Also, front page? Wow. Must be a slow day on Hacker News, huh? I'm honored, but I don't really think the article has the "substance" to justify a front page ranking.

[runevault]

Clojure articles seem to draw a lot of upvotes by default, to the point of silliness. I love Clojure but it's kind of bizarre how fast they draw upvotes here, since it isn't a Clojure site.

[m0th87]

How is Clojure debugging now? Last I checked, I couldn't get a reliable stack trace, and the advice I read online said "just step through it" or use somesuch tool, which is presumably not very helpful when you're trying to figure out why an hour-long application unexpectedly crashed. That was enough to scare me away.

[jshen]

I'm not sure what you mean by "reliable stack trace", but I've been doing clojure full time for the past 6 months or so. Our program needs to stay up and it is heavily threaded. In this context I haven't had any problems with stack traces and my app fits your description of hours long run time and some crashes.

[runevault]

There are still thick stack traces by default, but there are tools to help now.

http://clojure.org/libraries#Clojure%20Libraries-Category:%2...

[sbochins]

Never knew there was an issue with stack traces in Clojure. I only started programming in it several months ago. From what I've found, its much easier to wade through stack traces in Clojure. You can break out at different points in the stack and have a running repl with that environment. I've found this to be very helpful with debugging.

[tmountain]

A minor quibble from the post, but instead of doing this:

  cat $(find . -name "*.clj") > clojure.lisp

you can avoid the temporary file by doing this:

  find . -name "*.clj" | xargs wc -l

[technomancy]

wc doesn't leave out comments and newlines.