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

Pages: 1-4041-

Bad things about LISP

Name: Anonymous 2007-07-30 8:06 ID:E63qCOgk

Yes, I know Lisp is amazing satori, etc. But that's not the purpose of this thread. Here we list the crap things about Lisp (scheme, cl, whatever) and how we could improve it

1) Cannot produce independant binaries
2) Excessive parens can lead to an unreadable mess
3) Not much use outside of small configuration scripts
4) Not embeddable or extensible (biggest flaw yet IMO)


Name: Anonymous 2007-07-30 8:18 ID:Heaven

2) Excessive parens can lead to an unreadable mess
gtfo

Name: Anonymous 2007-07-30 8:22 ID:E63qCOgk

>>2
Only constructive discussion allowed in my thread, Lisp weenie.

Name: Anonymous 2007-07-30 8:24 ID:XL/Xvezb

(non-constructive)

Name: Anonymous 2007-07-30 8:33 ID:Heaven

Failed troll is failed.

Name: Anonymous 2007-07-30 8:36 ID:Heaven

>>1,3
sorry for being non-constructive in a shitty thread.
Try slashdot.

Name: Anonymous 2007-07-30 8:38 ID:Heaven

One word: the forced balancing of parentheses thread over.

Name: Anonymous 2007-07-30 9:04 ID:J5lzPyxy

THIS IS A DIRECT COPY OF MY BAD THINGS ABOUT PYTHON THREAD I STARTED MYSELF.

Name: Anonymous 2007-07-30 9:05 ID:J5lzPyxy

oh, yeah
the worst thing about lisp is all these idiot faggots learning it and telling everyone how great it is

Name: Anonymous 2007-07-30 9:08 ID:luaj/Gpb

1) wrong
2) yeah
3) wrong
4) wrong

Bad things about LISP: Modern languages are much better.

Name: Anonymous 2007-07-30 11:48 ID:9izknE76

>>1

1) Cannot produce independant binaries
Even C requires MSVCRT or the like (Windows).

2) Excessive parens can lead to an unreadable mess
Not with pretty printing and small functions (good code practice regardless). Further note: Perl code is a mess, C is a mess, C++ is even more messy. Lisp has the most homogeneous syntax there is.

3) Not much use outside of small configuration scripts
Whuat?

4) Not embeddable or extensible (biggest flaw yet IMO)
See ECL. But yeah, I agree, generally.

Name: Anonymous 2007-07-30 12:06 ID:f3uTN9lx

Even C requires MSVCRT or the like (Windows).
get a better compiler.

Lisp has the most homogeneous syntax there is.
http://ling.ucsd.edu/~barker/Iota/

Name: Anonymous 2007-07-30 12:26 ID:BOZPokeo

>>1
Not embeddable or extensible (biggest flaw yet IMO)
Simple enough so that you can implement it yourself instead of embedding. Should be 100-500 lines of code, depending on what you work with.

>>12
Lisp has the most homogeneous syntax there is.
Out of the practical languages.

Name: Anonymous 2007-07-30 12:36 ID:Heaven

Out of the practical languages.
lisp is not practical.

Name: Anonymous 2007-07-30 13:22 ID:9izknE76

>>14
Tell that to someone who is not intelligent.

Name: Anonymous 2007-07-30 13:23 ID:Heaven

Name: Anonymous 2007-07-30 13:29 ID:fv/yy8b3

Bad things about lisp:

it's outdated and replaced by Haskell

Name: Anonymous 2007-07-30 15:03 ID:BOZPokeo

Bad things about Lisp:

Scheme is fine, but Common Lisp is full of fugly legacies: "car"? "cdr"? "progn"? "mapcar"? Function value vs value? No forced proper recursion of functions in the standard? IMO Common Lisp kinda fails; Scheme with a series of extensions such as PLT wins.

Name: Anonymous 2007-07-30 15:11 ID:Heaven

>>18
Implementations of Common Lisp suck ass.

Name: Anonymous 2007-07-30 15:28 ID:J5lzPyxy

>>19
you haven't met SBCL which is an incredible implementation

Name: Anonymous 2007-07-30 16:03 ID:nH7TAGDC

>>18
That's what you get when you form a committee to define a language.

Name: Anonymous 2007-07-30 16:17 ID:ZJf7A6/x

>>18
Are you saying that Scheme doesn't use car and cdr?

Name: Anonymous 2007-07-30 16:45 ID:J5lzPyxy

>>22
whereas CL has FIRST, SECOND, NTH, and scheme has fucking LIST-REF lol

Name: Anonymous 2007-07-30 16:53 ID:PvMxTy4/

2) Excessive parens can lead to an unreadable mess

It wouldn't be such a mess is lisp "hackers" realised they could unindent closing parens.

Name: Anonymous 2007-07-30 17:22 ID:Heaven

>>24
you are an idiot

Name: Anonymous 2007-07-30 20:05 ID:Heaven

Random thoughts:

embedding:
   tinyScheme is primarily for embedding. GIMP included it.
   Lua is mainly for embedding, and its designers took
      inspiration from Lisp when they made the table the
      primary data structure the way Lisp makes the list
      its main structure.

parentheses
   There are various attempts to make it more readable, like
      pico: http://pico.vub.ac.be/
   Forth roughly matches Lisp in line count comparisons and
      abstraction. Although I think Lisp is more readable,
      some people think Forth is pretty clear.

Name: Anonymous 2008-04-19 18:49

lack of good libraries

Name: Anonymous 2008-04-19 18:53

I know you guys won't believe me, but I really did make this thread a year ago. I was trolling the Python thread.

Name: Anonymous 2008-04-19 18:57

>>28
This may surprise you, but I invented the ``I really did make this thread a year ago'' meme.

Name: Anonymous 2008-04-19 19:10

>>29
Fellate a pistol.

Name: Anonymous 2008-04-19 20:21

>>30
Wouldn't you feel    k i n d   o f   b a d  a b o u t   i t if I did?

Name: Anonymous 2008-04-20 23:26

1) Cannot produce independant binaries
Stalin.
2) Excessive parens can lead to an unreadable mess
Learn to indent.
3) Not much use outside of small configuration scripts
Emacs.
4) Not embeddable or extensible (biggest flaw yet IMO)
Embeddable Common Lisp.

Four WRONG statements.

Name: Anonymous 2008-04-21 0:17

>>31
You have been caught failing

Name: Anonymous 2008-04-21 1:55

>>33
YHBT

Name: Anonymous 2008-04-21 2:46

>>34
YHBT

Name: Anonymous 2008-04-21 3:33

>>35
s/YHBT/YHBMT/
YHBMMT

Name: Anonymous 2008-04-21 4:02

Name: Anonymous 2008-04-21 4:07

>>36
$_ = "=]=>%-{<-|}<&|`{/";
tr~ -/:-@[-`{-}~`-{/" -~;
eval $_;

Name: Anonymous 2009-03-06 15:18

Fine CHARACTER char define.

Name: Anonymous 2010-12-06 9:45

Back to /b/, ``GNAA Faggot''

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