freenode/#lisp - IRC Chatlog
Search
4:52:49
Harag
:aeth ... my answer to why lisp: Don't use lisp it will change your life! If you work for a boss he/she will sit you down in their office and give you a serious talking to for trying to sneak lisp into your projects! Once you start using lisp you will get very unhappy in your job when having to use other languages, your frustration levels will sky rocket. The other programmers will start avoiding you because they dont understand what you are blabbering about
4:53:59
no-defun-allowed
Harag: shit on the floor and hit the door, then start your own Lisper cooperative and put that dumbass out of business
4:54:42
pjb
Harag: do you realize that because you put the colon before the nickname, our IRC client won't match it, and therefore won't beep at aeth to notify him that you addressed him. So basically you're speaking in the desert.
4:57:15
Harag
If you run your own little business and you start using lisp you will be amaized at how quickly you get MVP's to clients, the clients wont be able to keep up, so you have to take on more projects to keep cash flow going and soon you will have tons of open ended projects and little cash. After a while you will start worrying that you are charging your clients to much because you are spending so little time on projects. Then when you drop your prices to be fai
4:59:02
Harag
just thought it would be fun to put the why lisp in human terms and in the negative...some reverse psychology ;)
5:12:01
Harag
...the other thing that will cause you internal conflict is when you come to the conclusion that a lot of times its just quicker to roll your own lib for functionality x, because learning how to use other peoples from reading their source code is tough going and there is so much of the functionality that you dont really need...etc
5:49:08
bmansurov
o/ Is there a more concise way of writing the following code (especially, removing the duplicate gethash function call):
5:51:23
pjb
bmansurov: symbols are used to name things, but they can name different things in different contexts.
5:51:58
bmansurov
pjb: I see. I thought since value is already present, why cannot I write (setf value 10)?
5:54:27
pjb
bmansurov: you could define a symbol-macro, but this wouldn't change the fact that the symbol gethash would be used twice in the expansion.
5:55:13
pjb
(macroexpand-1 '(multiple-value-bind (value present-p) (gethash 'a h) (foo value))) #| --> (multiple-value-call #'(lambda (&optional value present-p &rest #:ignore) (declare (ignore #:ignore)) (foo value)) (gethash 'a h)) ; t |#
8:22:41
shrdlu68
LdBeth: Who are "IRINA people"? Herbert Simon and Allen Newell also resisted the calling what they were doing "Artificial Intelligence", preferring to use "Information Processing", but there's a funny story about how their work was received at the 1956 Dartmouth conference.
9:04:21
aeth
to have "artificial intelligence" you have to define "intelligence" so I can see why people would prefer another term, if that was their reasoning.
9:20:00
shrdlu68
Ah, that would also include Simon & Newell: https://en.wikipedia.org/wiki/Logic_Theorist
16:12:55
pjb
You cannot define methods on system objects or build-in objects. Basically, you may define methods only on your own objects.
16:14:25
pjb
(defgeneric my-print (object stream) (:method (object stream) (print object stream))) and then add methods at will.
16:22:10
selwyn
in particular, not following the prescriptions regarding *print-circle* could lead to an otherwise unexpected unbounded amount of output to the printer which could, for example, break a REPL session
16:30:10
selwyn
no problem. well, actually i am not so sure about my most recent argument. but avoiding undefined behaviour is certainly reason enough to follow the rules.