News for hackers. Stuff that matters.
Re:Lisp in Small Pieces: Table of Contents and Code by dkarapetyan on Thursday November 13, 2014 @03:20AM (#8600470)
You're using some interesting words for something that is a tool to accomplish a task. You should continue to write code in Clojure and also other languages like C, Python, JavaScript, Ruby, C#, F#, etc. if you want to become a better programmer.

A programming language is a tool like any other and it is not magical or addictive. Your goal should be to solve problems by using the most appropriate tools for the job. Focusing on anything else I think is misguided.

Re:Lisp in Small Pieces: Table of Contents and Code by bulte-rs on Thursday November 13, 2014 @03:36AM (#8600514)
Yet, even carpenters can have favorite tools. I really enjoy hitting stuff with a large sledgehammer; that doesn't mean I use it to do everything... I just really like hitting stuff with a big hammer, makes it extra special when I can actually use it.

Same applies - imo - to programming languages. I use Ruby for most of my work since "it just gets the job done"; but I really love the moments I can work on one of my clojure projects.

Clojure is my favorite hammer at this moment, that might change to F#, Haskell, Go, <new language> anytime.

Re:Lisp in Small Pieces: Table of Contents and Code by dkarapetyan on Thursday November 13, 2014 @03:42AM (#8600520)
That's why I said one should program in a plethora of languages to understand the strengths and weakness of each paradigm and feature set. You wouldn't use a sledgehammer to put a nail in the wall for hanging a picture and similarly there are certain situations where Clojure or Ruby is not the right language.
Re:Lisp in Small Pieces: Table of Contents and Code by bulte-rs on Thursday November 13, 2014 @06:14AM (#8600934)
But imagine how much fun it would be to drive that tiny nail into the wall with that huge sledgehammer.

I don't disagree with you - on the contrary - but just wanted to point out that fun might be a great motivator for chosing a language.

Re:Lisp in Small Pieces: Table of Contents and Code by ehurrell on Thursday November 13, 2014 @03:50AM (#8600548)
In fairness there is some good context for wanting to get the 'magic', Lisps are talked about in such a context, as beautiful life-changing experiences, so it's understandable to be curious. I'd agree, the right tool for the job, and focus on the job, but the context is there to ask. Lisps as I've used them seem like powerful tools.
Re:Lisp in Small Pieces: Table of Contents and Code by dkarapetyan on Thursday November 13, 2014 @03:56AM (#8600564)
Yes, lisp dialects are powerful but there is no magic. The road to enlightenment is long and arduous and can not be put in an HN comment box. It's like I said in my original comment, the only way to get there is to just continue to write code and explore different paradigms and languages.
Re:Lisp in Small Pieces: Table of Contents and Code by pmoriarty on Thursday November 13, 2014 @09:42AM (#8601699)
I would not describe the road as long and arduous, so much as long and joyful.

I have never used a language a fraction as fun as Scheme (except for Common Lisp, which is also quite fun).

Re:Lisp in Small Pieces: Table of Contents and Code by ehurrell on Thursday November 13, 2014 @04:56AM (#8600732)
Yes, I agree, I think pragmatic discussion like this is important, the 'magic, beautiful, life-changing' hyperbole is probably better left alone in analysis I'd say.
Re:Lisp in Small Pieces: Table of Contents and Code by icebraining on Thursday November 13, 2014 @07:15AM (#8601118)
I think what you can enlightenment is what others are calling magic.