Conversation:
Notices
-
The !Lisp Curse http://t.co/i2h6wuRQ by @rudolfwinestock /via @CompSciFact
-
I sometimes wish there was a lisp dialect that was more like python: there's a general convention and one good way to do almost everything.
-
With a solid standard library (and of course good packaging... not that python is great there presently)
-
However I will disagree with the author on "emacs has not fundamentally changed in the last 20 years"
-
Emacs hacking is going through a kind of renaissance over the last few years, I feel.
-
@cwebber I'm only slightly accustomized with Python, but AFAIK, that is quite truthful remark.
-
http://identi.ca/url/73297577
-
@cwebber What's wrong with using guile?
-
@barryfm @cwebber What's right with using guile? (Common Lisp has strong conventions, btw.)
-
@jasonriedy That's not really an answer. I have no problem with Common Lisp, but it does not meet @cwebber 's requirement of one good way.
-
@barryfm I haven't used guile much, so I guess I can't comment heavily, but seems to be much more minimal in the "batteries included" aspect
-
I could be wrong though. Again, I don't know much about guile. I'd like to know more.
-
One heresy I really wish a lisp system had nailed down: *one* way to do OOP and (biggest heresy) dot notation.
-
I don't want (someclass-somemethod object args) or (callmethod object 'methodname args)... I want (object.method args)!
-
@barryfm @cwebber That there's only "one good way" is a myth even in Phyton, sorry.
-
@cwebber Guile has (method object args) with common lisp like generic functions, so you can do (append vbox widget)
-
@cwebber That's the risk that comes from being the first standard. When others decide to work differently, you're stuck.
-
@cwebber Also, binding tightly to the object isn't how CLOS works. That drives me nuts in languages that conflate packaging with dispatch.
-
It is a myth in "full completion of that idea". But aspiring towards it leads to a cleaner infrastructure.