51–60 of 143 posts
Every time, I see one of these links or videos, I feel the urge to learn Lisp. But after some time, I lose the motivation. I think that is because I don't know what benefit learning lisp will provide me concretely. Anyone has any suggestion?
Code as data is such a big deal that - whatever you say - I will never ever understand why we don't all do Lisps.
What's the most popular Lisp in use today? Does it come with a static compile type checking?
At least if based in 2016 GitHub popularity:
http://sogrady-media.redmonk.com/sogrady/files/2016/07/lang....
#1 Emacs Lisp
#2 Common Lisp
#3 Scheme
#4 Racket
Unless you consider Clojure a Lisp (yes it is, and no, it isn't...), in which case #1 would be Clojure, and then the others listed above.
Every time, I see one of these links or videos, I feel the urge to learn Lisp. But after some time, I lose the motivation. I think that is because I don't know what benefit learning lisp will provide me concretely. Anyone has any suggestion?
Do you like Python? Python is basically simplified Lisp. Common Lisp is Python plus first-class lexical closures (rather than second-class) plus true multithreading plus a real compiler so it runs much faster. Plus parentheses rather than indentation to delimit expressions; parentheses are much more versatile once you get used to them.
Earlier quoted context omitted.
People don't want powerful features because they can be misapplied, making a mess. These people aren't worried that they will make a mess of their own code, they are worried that they will have to deal with someone else's mess. What happens as you add more developers to a code base, with larger variance in ability and favored abstractions is going to be important in some cases, and irrelevant in others.
To expand a bit on this: Imagine that you're joining a project. It's been worked on by a team of 100 people for a decade. Half of those people were below-average programmers. Many were newbies in the language, and some were newbies to programming. And you're going to get to try to maintain this code. Now, do you want it to be written in a restrictive language, or in one that gives developers the ultimate amount of fr…
I wouldn't join this project, no matter what the language is.
Imagine it's a popular languae. Javascript or C code, for example. There are no true namespacing / packages and modules facilities in JS or C. It would be even worse than the theoretical nightmare you think Lisp would be. (Lisp has extensive namespacing facilities; code can be contained within modules that don't clash.)
If it was Java, you will see wrongly applied Design Patterns, leading to over-complicated, hard to mantain code.
No, thanks. I wouldn't accept no matter the languages.
Newbies to programming should be educated and trained, not incorporated directly into an important project.
23:43 "It really is incredible that we can go close to one order of magnitude" (to C)
26:00 Lisp code is faster than optimized C (quantum) programs when running on the QVM. For non trivial benchmarks (...) {Lisp faster} on an average of 40% percent.
30:00 quick explanation of quantum machine code
33:06 What is the team dynamics of using Lisp? "Condescencion: Lisp's number one enemy" (fun part)
"Some time between 2 and 6 decades ago, Lisp invented approximately all of the popular things in programming, some of which are just starting to make an appearance [long list of features follow]"
Really fun part follows.
35:41 things Lisp programmers tell the other programming teams
36:40 Interesting, beautiful comparison of using Lisp versus doing calligraphy with calligraphy pens.
41:21 Presenting internship program at Rigetti. Stressing the importance of first having a SBCL, Emacs, Slime, Paredit, and Quicklisp, before thinking how writing productive Lisp looks like.
43:33 Comments of interns after the internship, favorable to Lisp, as well as unfavorable comment. (Fun part here)
51:00 Explanation of what quantum computing is all about
This was a much more enjoyable video than I was expecting. The audio quality really had me tempted to skip, so I encourage others to not let that turn them away. The quote which I will paraphrase that "lisp is not freed from having to justify why you would use it." This is huge and the section before it going off about how condescension is a terrible enemy of the language is one that I would hope more people contempl…
I unplug my headphones jack halfway to turn failing stereo into good enough bi-mono.
https://askubuntu.com/questions/17791/can-i-downmix-stereo-a...
Earlier quoted context omitted.
To expand a bit on this: Imagine that you're joining a project. It's been worked on by a team of 100 people for a decade. Half of those people were below-average programmers. Many were newbies in the language, and some were newbies to programming. And you're going to get to try to maintain this code. Now, do you want it to be written in a restrictive language, or in one that gives developers the ultimate amount of fr…
> Many were newbies in the language, and some were newbies to programming. I wouldn't join this project, no matter what the language is. Imagine it's a popular languae. Javascript or C code, for example. There are no true namespacing / packages and modules facilities in JS or C. It would be even worse than the theoretical nightmare you think Lisp would be. (Lisp has extensive namespacing facilities; code can be conta…
Then you will never be employed, because that describes virtually every software project at a for-profit company.
too bad the audio quality is low..
Sorry about that. Our microphone/recording rig wasn't set up in time, and had to resort to a batter-powered lapel mic. We will try to at least duplicate the channel. I hope that the audio is at least relatively clear, and not muffled and incomprehensible!
Earlier quoted context omitted.
Do you like Python? Python is basically simplified Lisp. Common Lisp is Python plus first-class lexical closures (rather than second-class) plus true multithreading plus a real compiler so it runs much faster. Plus parentheses rather than indentation to delimit expressions; parentheses are much more versatile once you get used to them.
Python and Common Lisp are pretty wildly different in almost every social, technological, and philosophical sense.
This video was awesome, and entertaining as well, Mr. Tarballs-are-good/Symbol1cs/Stylewarning ("stylewarning" as a twitter ID made me ROFL). In particular, the comparison between calligraphy and Lisp programming was a very good one.
I've sent you a LinkedIn request, by the way. I'm the bald one in business suit.
