Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Lisp kills productivity!

Name: Anonymous 2011-08-06 2:53

Lisp goes against the human thought process. You must think in reverse to successfully write and read Lisp code!

Consider the famous REPL:
(loop (print (eval (read))))

People will typically think Loop-Print-Eval-Read, which is obviously wrong. They want to read left-to-right, not recursively. Thus, it's a write-only language. I'm an employer and if one of my applicants told me they were a Lisp programmer, I'd personally throw them out the door.

Name: Anonymous 2011-08-06 3:08

Just reverse the parenthesis if the left-to-right thing bothers you.

Name: Anonymous 2011-08-06 3:34

loop(print(eval(read())));
Totally different.

Name: Anonymous 2011-08-06 3:55

It's crystal clear. Maybe you're not too bright and it makes perfect sense that you don't want to be outsmarted by your employees.

Name: Anonymous 2011-08-06 3:55

In Symta you can do

read | eval | print | loop


Like in Bash. And Symta is still a Lisp dialect.

Name: Anonymous 2011-08-06 3:56

>>5
Of course, Symta has no `print` function, so it is read | eval | say | loop

Name: Anonymous 2011-08-06 5:25

It should have been called the LPER to avoid confusion.

Name: Anonymous 2011-08-06 5:50

>>3
Retard.

Not a Lisp programmer, but these should be the same:

(loop (print (eval (read))))
((((read) eval) print) loop)

Expand them out. The deepest one in both is read, thus that is done first. Then eval follows, then print, and then loop. Thus, they must be done in that order.

Also, BIDMAS/BODMAS/PEMDAS/whatever the fuck kids use now for the order of operations. Both are readable if you aren't fucking retarded.

Name: Anonymous 2011-08-06 5:59

>>8
((((read) eval) print) loop)
That would try to apply the evaluation of read to the eval function and so on, which is obviously incorrect.

Name: Anonymous 2011-08-06 7:51

>>8
((((read) eval) print) loop)
now it looks jewish.

Name: Anonymous 2011-08-06 14:23

>>4
There's a reason why there aren't any real jobs out there that use Lisp.

Hint: Lisp sucks

Name: Anonymous 2011-08-06 15:30

>>11
Then Java is great?

Name: Anonymous 2011-08-06 17:57

>>12
Yes. Java is fast, too.

Name: Anonymous 2011-08-06 21:24

>>2
)loop )print )eval )read((((

Name: Anonymous 2012-12-08 15:27

( ͡° ͜ʖ ͡°)

Name: Anonymous 2012-12-08 15:44


(defun rec-rev (item)
  (if (listp item)
    (reverse (map 'list #'rec-rev item))
    item))

(defmacro human-thought-process-compatible (&rest code)
  (rec-rev code))

(human-thought-process-compatible 1 2 3 4 +)

(human-thought-process-compatible
  ((((1 n -) factorial) n *)
    1
    (0 n eq) if)
  (n)
  factorial
  defun)

(human-thought-process-compatible 12 factorial)

(human-thought-process-compatible (((read) eval) print) loop)

Name: Anonymous 2012-12-08 17:00

They want to read left-to-right
i really don't want to bring on that topic again but truth is above all
hebrew is written from rigth to left...

Name: Anonymous 2012-12-08 21:58

Danken >>16. Thank should silence basement dweller >>1.

Name: Anonymous 2012-12-08 22:32

>>17
So the real Jewish programming is............ FORTH?

Name: Anonymous 2012-12-08 22:53

"people
This may be true of English, but some cultures still read right to left, and so it might be more intuitive for them anyway. You aren't very considerate, OP.

Name: Anonymous 2012-12-08 23:09

>>19
No. FORTH is read from left to right, like sensible languages. LISP is read from right to left, like Hebrew and other back-asswards languages.

Name: Anonymous 2012-12-09 2:07

(read (print (eval loop)))
ENTERPRISE QUALITY CONTINUATION PASSING STYLE

Name: Anonymous 2012-12-09 2:35

>>22

(call-with-fixed-point (lambda (f)
  (call-with-standard-output-stream (lambda (out-stream)
    (call-with-standard-input-stream (lambda (in-stream)
      (call-with-input-token in-stream (lambda (token)
        (call-with-evaluated-value token (lambda (value)
          (call-after-printing-value value out-stream (lambda ()
            (f)))))))))))))

Name: Anonymous 2012-12-09 2:36

anal lisps

Name: Anonymous 2012-12-09 3:50

>>24
Oh, I get it! It's because you're talking out of your ass!

Name: Anonymous 2012-12-09 5:05

"Human thought process", whatever that is, isn't left-to-right. There are many writing systems that work from right to left, in fact it was the primary way of writing before the advent of ink, as most people are right handed and they didn't use their off hands for chiseling etc. - with ink if you wrote the other way you'd smear what you wrote.

Name: Anonymous 2012-12-09 5:51

sub.domain.tld
2012-12-09
Universal Left Hand rule
nuff said

Name: Anonymous 2012-12-09 5:53

>>26
Shalom!

Name: Anonymous 2012-12-09 5:59

Lisp is parsed left to right,
each line from up to down,
and executed right to left,
moving its memory usage from down to up.

Name: Anonymous 2012-12-09 9:54

>>1
That is why did Symta: StdIn,read,eval,print,loop

Name: Anonymous 2012-12-09 13:20

>>26
``Most'' systems were actually not right-to-left, but rather left-to-right-to-left-to-right.  Phoenikian and early Greek inscriptions are arranged like that.  I have no idea why Arabs and other semithic Jews insist on writing right-to-left, because, as most of them are right-handed (or so I think), they do not see what they write, while I can see what I just wrote when moving my hand from left to right.

Name: Anonymous 2012-12-09 14:21

>>31
They're all secretly left-handed.

Don't change these.
Name: Email:
Entire Thread Thread List