4 ms·
>But don't try to introduce Lisp into your company, unless you are a cofounder of that company. It's a career limiting move. I think this is correct, unfortun
by gjvc 7y ago
>But don't try to introduce Lisp into your company, unless you are a cofounder of that company. It's a career limiting move.
I think this is correct, unfortunately, due to the place in history lisp occupied in the AI winter. As a result, it's looked upon as a failure, and people tend to dissociate themselves from such things, even when there is a body of evidence to the contrary demonstrating its efficacy.
Is that what you were alluding to or am I being too simplistic? I'm just trying to expand on your remark. :-)
- bitwize 7y agoPart of it is that, yeah, but part of it is the "nobody ever got fired by buying IBM" principle. In a corporate environment, you use what's established, period. Using something else is incurring unnecessary risk. Obscure languages have smaller ecosystems and talent pools, and ultimately, usually cost the company more money in the long run. So sharpen your Java, C#, and/or Node skills.
- kazinator 7y agoManagers in a current company don't what "AI winter" is. The whole "AI winter" meme is just a psychological complex in the mind of a few old-time Lisp coders. It has no relevance today.