[LISP] Unearthly forces

With lisp, every line is aethereal. The young lisper is enlightened in face of such realization. That a 10 line simple lisp program may do from one written in another language, even if the other language seems more elegant for the task (noting seems), is uncomparably more. The lisper may start abstracting away and writing powerful utilities and a program so complete and flexible at the same time, by adding 50 to 100 more lines of code. The equivalent work on another language would be tremendous. For the lisper this is natural. It's so natural which takes a part from oneself permanently. When the lisper must write code in some other language, the fear of the lines of code that must be written, and the hacks (quick and often unthink solutions to a problem) that must be endured, along with the pain of not being able to write in lisp, turn him useless. He is truly stumbled.

Imagine yourself being time-travelled back to 1500BC and living there with others. That is what being a lisper feels like when I write in your language.

Ah, free verse poetry.

Is this what satori is like?

Too bad people who had learned LISP and achieved Satori don't bother themselves with writing software anymore.
So we're stuck with jiggabytes of broken and poorly performing code in unenlightened languages on unenlightened platforms.

Too bad lisp has to copy everything so you can't even pass an array to a function without using the double memory than which C requires.

Giving up on assembly language was the apple in our Garden of Eden: Languages whose use squanders machine cycles are sinful. The LISP machine now permits LISP programmers to abandon bra and fig-leaf.

Haskell is much better due to its sheer elegance.

>>7
Explain the things of Haskell which you like that can't be done in lisp.

>>8
Typeclasses.
Subthread over.

>>8
$ instead of (((((((()))))))).

>>8
I've never had a runtime error in Haskell. If it passes Haskell's type system check, then it'll work.

>>8
I've never had a runtime error in Has*** Exception: stack overflow

>>12
Exception: Lulz not found[0x08003837]

>>13
Exception: back to /b/, please

>>14
Exception: EXPERT PROGRAMMER FUQIN ANGERED

>>7
sheer elegance
Haskell is a disgusting explosion of syntax. It would be pretty cool if it were postfix or used Lisp syntax though. An APL is fine too.

>>1
If I traveled back to year -1500, I'd like to think I'd manage to show those fuckers a thing or to. Teach them how to work iron, have them worship me as a living god that can make machines that move themselves with fire and water, those kind of things.
What I'm saying here is, seeing how I'd have knowledge of such superior technology, I'd manage to come up with something a little more impressive to show my inferiors than “My language has had closures and meta-programming for fifty years, while your more modern language has only had it for about twenty.”, Hmmm?

>>17
i would totally be able get laid 1500 years ago

>>16
Lisp's syntax is too much of an acquired taste, so much so that it contributed to prevent the language's use from being widespread. Even John McCarthy himself wanted to get rid of that eye-piercing syntax in favor of an algol-like syntax. And if Apple weren't such a bunch of faggots, Mac-hipsters would be raving about Lisp (well, Dylan) instead of goddamn Ruby right now.

>>17
You need to work on your history
>>18
you need to work on your maths.

>>16
lisp uses lisp syntax.
lisp is pretty cool.
come back once you've read SICP.

>>17
LISP isn't about closures.

24 Name: Anonymous 2011-02-03 0:08