Ten Reasons Not to Use Ruby or Python

1.) Lisp
2.) Lisp
3.) Lisp
4.) Lisp
5.) Lisp
6.) Lisp
7.) Lisp
8.) Lisp
9.) Lisp
10.) Lisp

We gained nothing of value by you making this thread, you know that? What's next, ``Ten reasons why the sky is blue''?

Is this listed in order of importance or alphabetically?

>>3
Numerically.

too bad lithp is for faggotth

>>5
Just think of how stupid you are, bumping a thread you don't like even though you think sage is an insult. Typical imageboarder.

>>6
Sage isn't an insult, it is simply polite. That being said, fuck off and die you faggot lithper.

>>5
is

>>6
I actually wonder what makes this one particular spammer (>>5,7) so persistent. Something about Lisp must hurt him in a special way, but he never quite expressed what it was... maybe he couldn't understand SICP, or maybe he couldn't set up Emacs or maybe he feels inferior to his peers who can perform those tasks. We will never know, unless he decides to give a honest answer instead of just spamming every Lisp thread (not that this particular thread has any value(everyone who uses Lisp for actual work already knows what the strengths and weaknesses of this particular family of languages is as well as how it compares with other languages), I could even imagine it was made by the same spammer so he could have a place to spam).

Lisp does not OOP as well as Ruby though.

>>10
We've got thousands of OOP systems and none of them would be as good as a bastardized version of Smalltalk's?

>>10
Not >>11, however, it should be pointed out that implementing OOP in a Lisp is a rather trivial exercise compared to other languages.

Besides, OOP isn't a Silver Bullet^TM. Learn and use different paradigms to your advantage. They all have their own strengths and weaknesses.

>>10
Huh, have you ever heard of CLOS? What about MOP that defines CLOS within itself? You can use it to build any object system you could desire as well as change the default one which is already quite powerful.

>>9
I actually wonder what maketh thith one particular thpammer (>>5,7) tho perthithtent. THomething about Lithp mutht hurt him in a thpecial way, but he never quite expreththed what it wath... maybe he couldn't underthtand THICP, or maybe he couldn't thet up Emacth or maybe he feelth inferior to hith peerth who can perform thothe tathkth. We will never know, unlethth he decideth to give a honetht anthwer inthtead of jutht thpamming every Lithp thread (not that thith particular thread hath any value(everyone who utheth Lithp for actual work already knowth what the thtrengthth and weakneththeth of thith particular family of languageth ith ath well ath how it compareth with other languageth), I could even imagine it wath made by the thame thpammer tho he could have a place to thpam).
fuckin' fag

>>14
You do sound hurt.

>>15
u sound buttranged go drinjk ur sperm bottle u norton commander etc.

>>14
expreththed
jutht
imagine
place

You've never actually heard anyone speak with a speech impediment before, have you? "ekthprethed", "thutht", "imathine", "plathe".

>>17
I have, but I'm too lazy to do it right, faggot.

>>18
Please refrain to show your retardation to the world!

Two reasons not to use lisp:
1.  )
2.  (

>>20
/thread

>>20
Shift your keys, I only have to press [ which is as easy as pressing any key, I don't have to close any paren because paredit does it for me, and the parens themselves can be made of a greyish/lesser visible color so that you only look at the indentation (which is automatic, but you can control it in various ways).

>>20
Two reasons to use lisp:
FTFY

Two reasons to not use FIOC:
1. 0x20
2. 0x09

>>22
fuck off and die already, don't you understand your language is fucking dead. get the fuck out.

>>25
“The most recent version is SBCL 1.0.48, released May 09, 2011 (release notes).” http://www.sbcl.org/

>>26
it only takes a few minutes for brain death.

>>27
Lisp is 53 years old, a little longer than a few minutes.

>>28
Ignore him. He's one of those faggots who talks shit about Lisp but programs in it anyway.