3 ms·
The claim was not about popularity or even familiarity, it was that Lisp syntax is so utterly alien, it's the primary thing that stands in the way of lisp adopt
by pvg 9y ago
The claim was not about popularity or even familiarity, it was that Lisp syntax is so utterly alien, it's the primary thing that stands in the way of lisp adoption.
I'm not worried but I appreciate the concern, I guess.
- kazinator 9y agoRight, just like syntax like FOO=$(command ${path#${path#/*}}) stands in the way of Unix shell adoption. Also, this one hinders HTML adoption: <foo bar="attr"></foo> This kind of thing (a direct snippet from the Linux kernel Makefile) hinders GNU Make adoption: $(if $(wildcard $(objtree)/.config),, $(error No .config exists, config your kernel first!))
- KirinDave 9y agoThe world is unjust, that's for sure. I look at the loader code I use in haskell w/ optparse-applicative and how much better it is than anything I've used in my damn life and I say, "Why is this considered unusable?"
- pvg 9y agoIt wasn't my claim so I'm not sure why you're explaining my point to me.
- KirinDave 9y agoProbably the thing stopping wider lisp adoption today is how very difficult Clojure is to learn (and how very off-on-a-limb PLT Scheme is).