Hacker News new | comments | show | ask | jobs | submit login

According to his post to the list, Mr. Yegge is responsible for the attitude transplant that the Python community has experienced. It's amazing what he can accomplish from his desk, dashing off memos to language communities. Jack Welch wishes he had that kind of power as CEO of GE.

The most puzzling thing he says is that Clojure's language adoption efforts have been a failure because Clojure is over three years old and hasn't broken the top ten in some pointless programming language survey.

How long did it take Python to get there? I'm guessing at least a decade. And does it even matter?




Beyond that, I'm pretty sure Clojure got rolled into Lisp on Tiobe, which is why it had such a big spike a while back.


The issue with Clojure is that it really gained too much popularity before it was ready. Ready has a lot of implications. IDE support, debuggers, libraries, documentation, books, etc. While it is a good language and has a number of things going for it. It seems that the books and community added too much hype too soon. This caused new users to come, then go.


I don't know if I agree with you that Clojure's too popular right now, but I completely agree with you that the phenomenon exists in general. Rails back in the early days experienced a huge influx of PHP refugees, who significantly lowered the signal-to-noise ratio in the community.

I use a language's Freenode channel is a general barometer of the state of its community's health, and I notice no more questions from bandwagon jumpers who have no clue whatsoever of what they're getting into on #clojure than I ever did on #scheme. I use those two channels for comparison because the sort of questions in question are similar: based on received assumptions that are counterproductive to being effective.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: