News for hackers. Stuff that matters.
Re:How Ruby Borrowed a Decades Old Idea From Lisp by npsimons on Tuesday September 18, 2012 @10:19AM (#4538101)
"It's [2012], and programming languages have almost caught up with 1958." -- paraphrased from, oh, you know, some guy :)
Re:How Ruby Borrowed a Decades Old Idea From Lisp by JoeAltmaier on Tuesday September 18, 2012 @10:26AM (#4538150)
DOn't imagine the reasons languages are different from List is that nobody knew any better.

Programming in Lisp is like programming in assembler. Reading it is worse. The learning curve is tremendous.

Languages serve lots of demographics, not just comp-sci wonks.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by KirinDave on Tuesday September 18, 2012 @11:27AM (#4538585)
When did the shift that makes this okay happen? Once upon a time, people who knew a lot about computer science were respected and praised; people tried to emulate their algorithms, coding style and planning.

Now, they are "wonks" for knowing a slightly different (and demonstrably effective) style of programming.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by aaronblohowiak on Tuesday September 18, 2012 @02:13PM (#4539616)
>When did the shift that makes this okay happen?

Now that there are millions of programmers. Programming shifted from a fine art to a pop art, to crib something from Alan Kay.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by JoeAltmaier on Tuesday September 18, 2012 @11:47AM (#4538723)
Hey! No offense meant. Its just true that a lot of programmers are not CS-trained. So not the target demographic of Lisp.
Re:How Ruby Borrowed a Decades Old Idea From Lisp by Jtsummers on Tuesday September 18, 2012 @11:54AM (#4538766)
I would contend that not being CS-trained doesn't eliminate them from the pool of people who could benefit from knowing Lisp and similar languages. As a programmer, unless you just want to be outclassed in a few years, you have to stay on top of developments in the industry and the history of the industry. Knowing the languages that modern languages pull their tricks from is one such way. And it doesn't take a CS degree to do that with many of the resources being put out these days.
Re:How Ruby Borrowed a Decades Old Idea From Lisp by JoeAltmaier on Tuesday September 18, 2012 @02:47PM (#4539820)
Same argument for any hot language. Who keeps up on them all? Excuse my french, "CS wonks"

The rest of the crowd is trying to ship code, in the toolset they have some facility with. That toolset has to be available, easily digestible, hopefully targeted at their problem space.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by dalke on Tuesday September 18, 2012 @12:01PM (#4538803)
If someone is a biology researcher who does some programming for their research, does that programmer need to stay on top of developments in the software industry? Or know the history of the programming field ... as well as keep up with the biology field?
Re:How Ruby Borrowed a Decades Old Idea From Lisp by Lio on Tuesday September 18, 2012 @12:58PM (#4539190)
Well I guess that depends on what you're doing within you're research.

In bioinformatics knowing about, say, functional programming and parallel algorithms could be really useful where data coming out of sequencers is growing faster than Moore's law can keep up, if you want to scale across many cores as efficiently as possible.

Or graph theory, or... any number of useful techniques waiting for an application.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by dalke on Tuesday September 18, 2012 @05:33PM (#4540639)
Certainly. But most aren't so inclined. Most need a way to glue together existing components. For example, "make a web connection to X, call command-line program Y, and use a shared-library extension to do Z. Plot in Excel." The result might be very useful scientifically, and it's definitely programming, but there's no real reason to learn about lambdas, s-expressions, and monads.
Re:How Ruby Borrowed a Decades Old Idea From Lisp by dfox on Tuesday September 18, 2012 @07:10PM (#4541054)
You would be surprised how often non-CS researchers doing some programming use languages that are essentially Lisp with weird syntax (R, Mathematica...). Which I think exactly demonstrates that you don't need any knowledge of history or modern developments in computing to benefit from Lisp.
Re:How Ruby Borrowed a Decades Old Idea From Lisp by neverm0re on Tuesday September 18, 2012 @02:40PM (#4539779)
You do not need to be a CS major to appreciate Lisp.

I've had a number of fun conversations discussing and demonstrating Scheme with novice and 'rank-and-file Java/C#' types. The ones who find programming languages fun in themselves are the sort of people who light right up when they're introduced to something like Scheme. That's really all it takes is just a bit of passion and curiosity to make the leap.

In my experience, professional folks I've spoken to have either never heard of Lisp or have associated it with antiquity. You'd be very surprised who'd appreciate being shown new ways of doing things.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by KirinDave on Wednesday September 19, 2012 @07:10PM (#4546027)
I don't think the target demographic of Lisp is "CS-trained" people. Do you? Why? Because functional programming, which is actually a lot more like the math everyone else learns, is somehow for "wonks?"

When you say things like this, part of me hears you saying, "I have not invested time learning this skillset. However, people argue I should. So I have decided said people are 'wonks,' and therefore I can safely dismiss them." Basically anyone with any differentiation from your skillset falls into that definition.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by andrewcooke on Tuesday September 18, 2012 @12:04PM (#4538819)
this makes no sense. on a purely personal, self-development level, you're talking yourself out of opportunities for no gain.

there's nothing magical about lisp compared to other languages. to read it you don't need a cs degree and you don't need vast levels of intelligence - you just need practice. after a while it becomes quite clear.

you're free to think whatever you want, of course, but this kind of negative attitude - "it's for the smart people, not me" - just means that you lose out.

lisp itself is not that far from a language like python (or, i guess, in the context of this thread, ruby) once you get used to it. it's really not rocket science. all you're doing here is harming yourself.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by JoeAltmaier on Tuesday September 18, 2012 @12:09PM (#4538863)
No, I don't reject it. I'm simply making the point that, still, some people (the majority of people) are not up to Lisp. Most folks never read the manual, just hop on board and start coding.

So, thus, the (Very) slow acceptance of Lisp.

Re:How Ruby Borrowed a Decades Old Idea From Lisp by blacksmythe on Tuesday September 18, 2012 @05:45PM (#4540696)

  >> The learning curve is tremendous.
Try "Land of Lisp" http://www.amazon.com/Land-Lisp-Learn-Program-Game/dp/159327...
Re:How Ruby Borrowed a Decades Old Idea From Lisp by yarrel on Tuesday September 18, 2012 @10:57AM (#4538398)
"Practical Common Lisp" is a good introduction to the power and readability of non-wonk Lisp.
Re:How Ruby Borrowed a Decades Old Idea From Lisp by alberich on Tuesday September 18, 2012 @01:02PM (#4539215)
Agreed. It makes CL look way easier than assembly :D

edit: not that I consider it to be like assembly, really.