15 ms·
Why Racket? Why Lisp? (2014)
- izietto 12y agoI love this site, it's so simple and beautiful
- nickbauman 12y agoI think the hardest thing for people to get for programming in Lisp is the immutability. Once you get over that hump, everything is downhill. From the outside, the parenthesis seem pedantic but it's completely superficial. You will stop noticing them in a few hours, if not days.
- mbrock 12y agoAre you perhaps coming from a Clojure perspective? Scheme is no more inherently immutable than, say, JavaScript. Many Scheme programs I've seen use mutation quite liberally. Immutability is a useful pattern in lots of languages and situations, but Lisp per se doesn't particularly enforce it.
- adrianm 12y agoIndeed. Common Lisp is similar with regard to the proliferation of mutation.
- marijn 12y agoIt in fact takes it to amusing extremes, allowing you to mutate even the strings associated with symbols. (setf (char (symbol-name nil) 1) #\U) (Though I guess that could be taken as being the same thing as doing nonsensical pointer arithmetic in C -- you simply should know better.)
- mbrock 12y agoI'd point out that Common Lisp, kind of like Smalltalk, is a highly dynamic environment that has historically been used as an operating system in itself. That's one reason why the system is so mutable—you don't want to have to relaunch it even to modify core functionality.
- adrianm 12y agoI actually don't view mutation in Common Lisp as a downside. I find writing high performance (usually numerical, but sometimes not) code in Clojure to be painfully obtuse compared to Common Lisp, but I love Clojure otherwise. Writing highly optimized code can be quite elegant in Common Lisp, and I appreciate that when the problem at hand calls for it.
- informatimago 12y agoActually, this expression is non-conforming: you must not try to modify the string returned by cl:symbol-name. "non-conforming" means you will get different results in different implementation, perhaps something like a nasal dragon, or perhaps an error signaled, or perhaps some more benign behavior. $ clall -r '(progn (setf (char (symbol-name nil) 1) #\U) (quote nil))' CLISP Attempt to modify a read-only string: "NIL" ECL Detected access to an invalid or protected memory address. Clozure Common Lisp --> #|symbol not found in home package!!|#COMMON-LISP::NUL Armed Bear Common Lisp --> COMMON-LISP::NUL CMU Common Lisp --> COMMON-LISP::NUL SBCL --> COMMON-LISP::NUL Some implementations will gladly and blissfully modify the symbol name, and your program will break because it cannot intern the original name anymore (not the best behavior for an implementation IMO); some implementation will detect the non-conforming access. Worse could have happened (remember, you are on the Internet so you can be located by geoip/gps/wifi, and missiles silos can be hacked by botnets). But otherwise indeed in general, mutable lisp objects are mutable, and you can implement mutating algorithms as well as purely functional algorithm. Foremost, you can have an hybrid approach, using what's best to solve the current problem.
- PuercoPop 12y agoRacket also defaults to immutable cons and you have to require set-car! and friends. But I agree, most Lisps do not impose/favor immutability
- mbrock 12y agoAh, right, but that doesn't mean the language is immutable to the degree that it would make for a steep learning curve. Mutating cons cells is arguably an obscure feature; you are free to mutate variables, vectors, structs, tables, and so on (even if you might have to specify that you want mutability).
- PuercoPop 12y agoMy experience with racket is certainly not one of steep learning curve. Plus it is _thoroughly_ documented. If I had to recommend a Lisp implementation for someone that wants to learn a Lisp it would definitely be Racket as it is easy to install (and works on windows), has great documentation and a super friendly and interesting community. The only thing I'm not fond of Racket is that compared to CL w/ Slime it feels way less interactive, a step up from Python, but still not CL (nor Smalltalk) But lets focus on the positive, the OP is highlighting that the trite criticism of non-lispers about parens is bogus.
- nickbauman 12y agoPerhaps I am but even Clojure is not "purely functional" in that respect.
- jlarocco 12y agoLisp is not an immutable language. There's setf and setq for assigning; nconc, nsubst, and the destructive list operations; rplaca and rplacd; etc. It's easy to write Lisp that doesn't mutate (let), or use constructs that hide it (dolist, dotimes, etc.), but mutable data has been in Lisp since the beginning. That said, there are languages in the family that don't allows mutation, but they're a small minority.
- nickbauman 12y agoClojure isn't immutable either. It favors immutability, though, and has strong opinions directing the developer away from mutable state.
- adregan 12y agoPrevious discussion can be found here: https://news.ycombinator.com/item?id=8206038 https://news.ycombinator.com/item?id=8206038 Have noticed quite a bit more buzz about Racket and Lisp very recently around here. It's always been something I mean to explore.
- nickbauman 12y agoI go to my local Clojure meetup. Last time I sat next to a guy who uses Racket in his day job. He said "If I didn't know what the problem was and was asked to pick the language beforehand, I'd pick Racket. I still like Clojure a lot." Didn't get a chance to unpack that with him.
- Yuioup 12y agoI think it's because of this: https://news.ycombinator.com/item?id=9220468 https://news.ycombinator.com/item?id=9220468
- melling 12y agoYes, if John Carmack built something with Racket and liked the results, it does pique one's interest. There are a lot of tools and languages to evaluate and so little time.
- s_kilk 12y agoWe seem to be on a Racket buzz lately, and I like it. I feel more inspired to dig further into Racket. I'm already pretty good with Clojure, so can anyone who knows both languages well comment on the ups and downs of learning Racket after learning Clojure?
- luxbock 12y agoThis is a blog post by technomancy, the original author of Leiningen, exploring Racket as a new language: http://technomancy.us/175 http://technomancy.us/175 EDIT: Wrong link. This one might be interesting as well so I've left it here: http://technomancy.us/169 http://technomancy.us/169
- Chris911 12y agoWhat is a good resource to learn Lisp for an advanced (non Lisp) programmer? Most guides for most languages only cover declaration, simple functions and tiny applications. I want something that quickly goes through the basics and skips to advanced uses in bigger codebases.
- mrottenkolber 12y agoPractical Common Lisp by Peter Seibel: http://www.gigamonkeys.com/book/ http://www.gigamonkeys.com/book/
- nemoniac 12y agoPCL is a good book but too wordy for my taste. Paul Graham's ANSI Common Lisp will get an advanced programmer up to an advanced level more quickly and efficiently. http://www.paulgraham.com/acl.html http://www.paulgraham.com/acl.html
- mrottenkolber 12y agoI'd say both are essential, but PCL should be digested first (no need to read every paragraph). On Lisp is IMHO a lambda power user guide and not a good general introduction to CL.
- nemoniac 12y agoNote that I recommended the book "ANSI Common Lisp" for an advanced (non Lisp) programmer, not "On Lisp". That aside, I agree with your description of On Lisp.
- wtbob 12y agoI'll second PCL. It really is incredibly good. Unlike some other introductions to Lisp, which tend to be of the algorithmic, CS side of things, PCL approaches things from more of a scripting/software-development side. Common Lisp really is a great developer's language, and PCL helps show why. Peter Seibel's a great writer, too.
- wehadfun 12y agois there a tl;dr. After about 45 secs of reading author did not answer why racket or why lisp
- nickbauman 12y agoIt's simpler than using the language you're probably using now. I cannot think of a higher praise for any design problem is that it's solved more simply with Y than X.
- qznc 12y agoForth is even simpler.
- innguest 12y ago1 - Everything is an expression so it's easier to snap code together. 2 - List based = flexibility, get more done faster because lists are simple and everywhere 3 - Strongly nudges in the direction of functional programming 4 - Rocking documentation, advanced libraries 5 - The Dr Racket GUI IDE 6 - X-expressions (don't know what they are) 7 - Hygienic macros 9 - Easy to write powerful DSLs 10 - Many low hanging fruits to contribute
- Moral_ 12y agoDr Racket is a horrible IDE. Routinely uses ungodly amounts of ram, ever try scrolling through your code because it spends 30 seconds in some paren matching loop.
- mbrock 12y agoI wouldn't say "horrible." I haven't used it for large projects, only for tinkering, but for that purpose, it's excellent.
- klibertp 12y agoUnfortunately I have to agree here. I abandoned DrRacket for Emacs racket-mode and geiser because waiting for DrRacket to finish whatever it was doing became too much for me. On the other hand, as an Emacs user, I'd probably do this even if DrRacket was much better optimized than it is :)
- j2438 12y agoI have so far stuck with Clojure instead of a Scheme primarily because of the nice literal syntax for maps, sets, vectors, and regexes that Clojure supports. I don't want to give that up and just use cons/car/cdr. And also, last time I looked at Racket, it seemed very focused on academics. I just wanted to write some simple Scheme in a .scm file and try it out (a script), but I think I had to choose a language first (maybe a line at the top of the file? Don't recall) --- the Racket ecosystem seemed off-putting.
- innguest 12y agoI'd encourage you to give it a longer try. When selecting a language, just pick R(5,6,7)RS and you're set. Liking syntax sugar is hardly a reason not to use the language with the most powerful macros around. You can write macros to provide nice literal syntax for whatever you want - this is part of the fun.
- j2438 12y agoHave not yet learned to use or appreciate macros. The idea of everyone having to come up with their own syntax for such commonly-needed things as, say, hashes, seems counter-productive to me. That would lead to everyone's code looking like a different language.
- innguest 12y agoI never said "with lisp, everyone has to come up with their own syntax for commonly-needed things". But it sounds your mind is already made up by hypothetical prejudices. You said you stick with Clojure over Scheme on account of some syntax. I said you can have that syntax in Scheme. You then said the non-sequitur "the idea I created in my mind of each individual user coming up with their own syntax is absurd", which I agree with. I don't know what to tell you but you seem confused. What you said is not a response to what I told you. I eliminated the difference you complained about, and you complained that in Scheme it's possible to solve the issue you have with it. There's no pleasing some people.
- _djhrtmn 12y agoHas anyone tried to use Butterick's Pollen and written about it? The idea of debugging your website with racket as you write markup and styles seemed really interesting alternative to what I do; write styles, refresh, and then refine the stylesheet by incrementally adding changes with the inspector and then copying them to my stylesheet.
- fa 12y agoI'm working through the admittedly beautiful and very thorough documentation [1]. It's a very simple idea, really: you write your document and sprinkle racket s-expressions wherever you want. You can put your definitions at the top of your document, or in another file. You describe your templates in Racket also, because like Butterick says in his RacketCon video [2], "S-expressions and XML are the same thing". You can use tags that you haven't defined, they just get placed in the resulting HTML. You still have to roll your own CSS and any JavaScript. As far as I can tell it doesn't help you out with things like keeping track of footnotes numbering or citations and such: you roll your own for things like this, Pollen is no LaTeX. This is partly why I say it's a really simple system. It makes a certain set of web authoring things simple, but it doesn't try to be a one-stop shop, which is excellent because this makes it a supremely flexible tool. It also has some backend fancy sauce where you can save your file and refresh the page [3]. Also I admit I'm not really a big fan of DrRacket: I've just been using it for the tutorials because I have no idea what to expect from Racket, but I'm slowly moving to Emacs, and Racket seems to work fine there. Definitely worth checking out Pollen if only to get a light introduction to the thoroughness of Racket documentation (they definitely do things differently in Racket-land!), but stay for the tools you need to roll your own ultimate static blog generator. (Also, completely unrelated: cool video and cool title at another RacketCon 2013 talk: "Racket on the Playstation 3? It's Not What you Think!" [4].) [1] http://pkg-build.racket-lang.org/doc/pollen/ http://pkg-build.racket-lang.org/doc/pollen/ [2] https://www.youtube.com/watch?v=20GGVNBykaw https://www.youtube.com/watch?v=20GGVNBykaw [3] I've made a request for no-refresh updates: https://github.com/mbutterick/pollen/issues/35 https://github.com/mbutterick/pollen/issues/35 [4] https://www.youtube.com/watch?v=oSmqbnhHp1c https://www.youtube.com/watch?v=oSmqbnhHp1c
- 12y ago
- SeanLuke 12y agoFor more on the per- ils of taxing reader patience, see WHY DOES TY- POGRAPHY MAT- TER This quote, hyphenated as is, provides all sorts of opportunities for snark. Instead I'll just note that it seems Pollen needs work. It's far too eager to hyphenate; doesn't protrude hyphens, commas, etc.; and doesn't use TeX-style paragraph-level optimization. Not being able to identify the bounds of hyperlinks is also a strong source of irritation.
- yoanizer 12y agoI have a feeling people tend to over estimate the importance of language choice. Might be just me though.
- lobo_tuerto 12y agoWould you have a look at this? http://www.paulgraham.com/avg.html http://www.paulgraham.com/avg.html
- dang 12y agoMany people agree with you but I have the opposite view. Of course you can write any program in any Turing complete language, but the programs people do write in a given language tend to have a family resemblance to one another. Therefore if we want different kinds of programs we should have different languages. A given language makes certain ideas easier or harder to formulate, and thus easier or harder to have in the first place. So the language constrains not only how you think about your program, but what you think—and thus what the program itself becomes. Platforms, communities, and culture also help determine these things, but they're not independent of the underlying language.
- allemagne 12y agoSome have also said that the human language you speak has an effect on how you think, but that's pretty controversial among linguists if not altogether discredited. I have no doubt the difference among human languages and programming languages could be completely different, but is there any concrete example you could give of an idea that is easier to express in one programming language than in another?
- dang 12y agoIMO the analogy to human languages is a distraction and best avoided, since we're not able to say meaningful things about both. > is there any concrete example you could give of an idea that is easier to express in one programming language than in another Sure. Since this thread is about Lisps: writing code that works with other code is an order of magnitude easier in Lisp. Therefore people tend to do it a lot more.
- codeshaman 12y agoIt's about a month since I've started seriously diving into lisp. The last couple of weeks I've spent my days reading 'The joy of Clojure', Structure and Interpretation of Computer programs, lots of tutorials and documentation, playing around in the repl + experimenting with all kinds of frameworks and libs in clojure (eg. Om). I've spent today implementing the brainfuck interpreter in Racket. I can't explain it, it's like something is calling me - 'learn lisp. now.'. Given the amount of Lisp code read/written and the relative novelty of it, I'm dreaming lisp code and the arguments to functions are actual physical things, which are then mapped, reduced, recursed or expanded. Literally, I think I'm going crazy. I can fluently write x-platform C++, Javascript/CoffeeScript, Objective-C, Java, Pascal, VB and everything in between. But never have I experienced this kind of mental strain/obsession as I do now with lisp. But. Seems like I'm not alone! Given the amount of lisp news lately on HN, I fell like more and more people are going through what I'm going. Seems like we here on HN follow a common mental pattern and suddenly everyone's talking/learning lisp. As interesting as learning lisp is, this 'group preference' thing is even more interesting to observe.
- vidarh 12y agoIt's not so sudden. HN itself is written in a LISP [1], and Paul Graham's pre-YC claim to fame was Viaweb, a store platform written in LISP that became Yahoo Stores. This community has been above-average LISP friendly for a long time. LISP's also has a long history of popping up all over the place because they are extremely implementation-friendly (if you want to write a simple language; if you want to make things fast they get trickier, thought by no means impossible) given the simple syntax. So you'll also find a lot of people (like me) who don't really like LISPy languages, but who still end up dabbling with related technologies occasionally (my very-slowly-in-progress Ruby compiler uses s-expression syntax (though no LISP semantics to speak of) to express a tiny language to implement some of the lower-level plumbing to bootstrap the Ruby core classes, for example) [1] http://arclanguage.org/ http://arclanguage.org/
- Adlai 12y agoIt's spelled 'Lisp'. There has been zero overlap between people writing "LISP" and people writing lisp code for about half a century.
- ims 12y ago> (x + (if is_true(): 1 else: 2)) [is invalid in Python] because the if–else conditional is a statement, and can only be used in certain positions. Point taken, but troll-mode pedantry: (x + (1 if is_true() else 2)) would be valid :)
- Xophmeister 12y ago...but, in that case, the `X if Y else Z` syntax is considered to be an expression in Python. You can't, for example, omit the `else Z` part. In Haskell -- again, in which everything's an expression -- conditionals are the same, just written in the "normal" order: `if Y then X else Z`.
- Scarbutt 12y agoHow production ready or mature are Racket libs for creating CRUD web services? skimming through the Racket website one can see Racket has the basics, a http server and a library for interacting with databases like postgresql, as someone relative new to programming/webdev, would I face to much "reinvent the wheel" versus Clojure or Javascript?
- mkozlows 12y agoDepends what you're doing. It doesn't have the depth of libraries of the JVM or JS, so there'll be lots of "oh, can't use that technology" or "is this 3-year-old unmaintained library still going to work with Mongo?" moments.
- wellpast 12y ago> What's in it for me? Expressiveness. I appreciate the author's wanting a more explicit and practical answer to this question, but I don't think his answer here ("expressiveness") does any better job than the other explanations he criticizes. > But [learning Lisp] also requires an investment of about 100–200 hours. That's asking too much. No, it's not. That's how long it takes sometimes, or longer. Why do we all expect answers and understanding to come so quickly and easily? It'd be a nice world otherwise, but almost always enlightenment comes at a cost: patient focus and study.
- AnimalMuppet 12y agoSure, that's true. But the problem is, there are dozens of things telling me that, if I invest that kind of time in them, they'll pay me back. Which one(s) should I pursue? In order to decide, I have to have some explanation of the benefits that I can grasp (at least in the abstract) before investing 100 hours. "Invest 100 hours and then you'll see why you should have done so" is not a sales pitch that will win with very many people.
- marcosdumay 12y agoWhy do you expect things that really improve your life to come with sales pitches?
- AnimalMuppet 12y agoPeople are usually eager to recommend things that they feel really improved their life. If you, for example, read HN, you see "sales pitches" (in the broad sense) all the time.
- marcosdumay 12y agoYes, that's true. But it's both naive, arrogant, and rude to require those "sales pitches" to be good. At the end of the day, it's up to you to decide what's better for you. If you try to outsource it, you'll discover that the best sales pitches around are for dead-end technologies. At the other side of it, people giving you those recommendations really have no better way to explain it. PG has an well known essay about language power, but even that isn't very precise. Some kinds of knowledge you really have to know before you understand what they are good for.
- dang 12y ago"Paul Graham’s programming language Arc, a dialect of Lisp, was built on top of Racket." Since that statement occurs in a section about Racket languages, I should probably clarify. Arc isn't technically a Racket language—that is, it doesn't use any of Racket's facilities for defining new languages. It compiles to Racket (and so you're all using it right now), but has its own distinct implementation. Historically, Arc wasn't built on top of Racket. I think pg may have started on Common Lisp, then went to Scheme 48, Mz Scheme, and so on. Probably the most accurate thing to say is that Arc was built in pg's head after years of thinking about Lisp. It doesn't have a particularly close relationship to any of those underlying platforms. Semantically it's closest to Common Lisp, but don't tell pg I said that.
- herdrick 12y agoI think it compiled to MzScheme first.
- dang 12y agoMzScheme came comparatively late. Here is a post from when it was Scheme48 and after it was Common Lisp: http://www.reddit.com/r/programming/comments/bstl/arc_lisp_dialect_by_paul_graham_hosted_on_scheme48 http://www.reddit.com/r/programming/comments/bstl/arc_lisp_d... A friend told me he used to track developments in Arc by noticing when pg had switched mailing lists. :)
- xrayspec 12y agoMZ Scheme was a precursor to Racket. Same people, AFAIK same core codebase. http://docs.racket-lang.org/mzscheme http://docs.racket-lang.org/mzscheme
- leanthonyrn 12y agoGood discussion of the advantages of Arc versus Racket. http://stackoverflow.com/questions/8555440/the-advantage-of-arc-over-racket http://stackoverflow.com/questions/8555440/the-advantage-of-... "I wish they had implemented Arc as a Racket module language since then you could actually develop in DRracket, debug, and make executables."
- PopsiclePete 12y agoHow does Racket stack up against Clojure? I like some of the special extended reader support for data structures, I dig the immutability, some of the concurrency stuff....I don't think immutability/concurrency is that typical for LISPs...for people who've tried both, which one do you prefer?
- pmelendez 12y agoI think people tend to use Clojure more because it has the Java VM and platform as support, which is a nice thing to have given its extension. The .Net world has IronScheme which is very stable and interesting too.
- AnimalMuppet 12y agoWhy hasn't XML been matched to Lisp very much? I think it's because Lisp programmers recoil in horror from XML. I mean, if you're already used to S expressions, XML looks disgusting. As verbose as Java, and less expressive. So I think most Lisp programmers look at XML and think "Ugh, don't get any of that on me..."
- agumonkey 12y agoIIRC, it was Naggum that said the issue with XML is the useless distinction between elements and attributes, leading to countless discussion, bikeshedding etc etc instead of actually solving problems.
- michaelsbradley 12y agoSee the resources organized under XML and Scheme, by Oleg Kiselyov: http://okmij.org/ftp/Scheme/xml.html http://okmij.org/ftp/Scheme/xml.html There is a Racket "package" (not quite a port) of SXML and SXSLT: http://pkg-build.racket-lang.org/doc/sxml/ http://pkg-build.racket-lang.org/doc/sxml/
- thuuuomas 12y agoTho in its infancy, Kawa scheme can "paper over" some of the XML in Android dev[0]. [0] https://www.gnu.org/software/kawa/Android-view-construction.html https://www.gnu.org/software/kawa/Android-view-construction....
- spain 12y agoAs someone who thinks Lisp is pretty cool and uses Emacs to study it and is about 100 pages into SICP: I still don't get it. Common Lisp macros went entirely over my head too. A programmable programming language? Aren't all languages like that? I've only been programming for a couple years so I'm afraid I might not recognize the value of Lisp until I use more of the "less powerful" alternatives.
- Ironballs 12y agoThe principal data structure of Lisp is a list which is written like this: (a b c d). Like the article mentions, when you see Lisp code you're in fact reading the same list syntax, only that, when the list itself is not quoted, the "a" is evaluated as a function, which is why (+ 1 2) behaves the way it does. If you quote the list by saying "'(a b c d)" then it is a list of symbols, so "'(+ 1 2)" does nothing. Hence, Lisp code is made of nested lists. When you think further about it, it means that Lisp metaprogramming facilities may do things just with plain list manipulation functions! So it's not about metaprogramming itself, it's that it's incredibly easy. This is what people refer as "code as data" and "homoiconicity" and so on.
- UNIXgod 12y agoI found the "Little Schemer" an enjoyable tour on exorcizing the power of lisp. Depending on how far down the rabbit hole you want to go there are a plethora of information in various AI memos as well as the READscheme web resource with the original LAMBDA papers (readscheme.org) which most certainly worth PRINTing if anything to get primed for SiCP.
- mbrock 12y agoLisp "advocacy" often touts the power of macros in an abstract and unconvincing way. Persuasion by explanation isn't very effective. I'm not very interested in persuading others that Lisp macros are necessary, and there are many languages I like to use that don't have macros. However! Yes, all programming languages are programmable. But Lisp tends to be unlimited in its programmability, in almost the same way that Unix is: if you have root, you can change anything. I'm pretty sure that in most Common Lisp systems, you can redefine large parts of the compiler at runtime. And so on. Syntactic macros are just one part. They can be extremely handy. Lots of Lisp systems use them well. Random examples: the DEFSYSTEM macro of ASDF; the DEFINE-EASY-HANDLER macro of Hunchentoot (a Common Lisp web server); the (controversial) LOOP and ITERATE macros; etc. Another somewhat random example: Movitz was (is?) a project to write an x86 kernel in Common Lisp. It actually included its own compiler. It defines a lot of macros for instruction definition [0] and uses them in code that I don't understand anything of [1] but is probably very clear to someone versed in assembly. Recently I've been trying to add some nice logging to a JavaScript program, and it's a typical scenario where the normal syntax is just annoying enough to make the code ugly and hard to scan—if I had macros, I could invent some other syntax. How to use macros is a tradeoff that I guess comes with Lisp experience, but they can be a powerful escape when the standard syntax is annoying, and a way to define your own DSLs without restriction. [0]: https://common-lisp.net/viewvc/movitz/ia-x86/def-instr.lisp?view=markup https://common-lisp.net/viewvc/movitz/ia-x86/def-instr.lisp?... [1]: https://common-lisp.net/viewvc/movitz/ia-x86/instr-add.lisp?revision=1.3&view=markup https://common-lisp.net/viewvc/movitz/ia-x86/instr-add.lisp?...
- omaranto 12y agoI'd be more interested in a "Why Pollen over Scribble?"...
- 10098 12y agoDon't waste your time with lisp. Learn lambda calculus and then see how these ideas are applied in actually useful imperative programming languages.
- evanspa 12y agoPretty ironic you've been posting here for 4 years to a site built with a language that's not useful.
- 10098 12y agoI'll believe that it's useful when unenlightened plebs like me start getting money thrown at them for writing lisp code. So far the industry seems to disagree with you about what's useful.
- lazzlazzlazz 12y agoThis site's backend could be built with dozens of different languages.
- mattnewton 12y agoI find all his digs at javascript funny since, at least the way I use it, javascript is basically an ugly-looking scheme. Javascript is responsible for my 'lisp enlightenment' with the language using first-class functions and closures, and the wide variety of precompilers. It strikes me as fashionable to hate on javascript. Java on the other hand, now that's a horrible language ;) ;)
- Zelphyr 12y agoI was thinking the same thing as I read it but I can conceded that its easy to overlook how much influence Lisp had on JS. I also find it mildly amusing to see all the Lisps written in JS that keep popping up lately.
- Scarbutt 12y agoJavascript isn't Scheme: http://journal.stuffwithstuff.com/2013/07/18/javascript-isnt-scheme/ http://journal.stuffwithstuff.com/2013/07/18/javascript-isnt... If Javascript were only an ugly looking scheme...
- fa 12y agoI too am amused by his opinion of JavaScript. A professor was moved enough to translate most of SICP to JavaScript and writes in its first chapter, "Above beyond these considerations, programming in JavaScript is great fun" [1]. I agree, and I'm enjoying going through this SICP/JS moreso than the original, as I can write solutions to the exercises in any old browser JavaScript console and paste them into a gist for safekeeping. [1] http://www.comp.nus.edu.sg/~cs1101s/sicp/ http://www.comp.nus.edu.sg/~cs1101s/sicp/