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.
[ Parent
| on HN ]
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.