3 ms·
I'm interested in your critique but it seems to me you've misrepresented two of his points. #2 compares Lisp's minimalism to any language with more complicated
by gruseom 19y ago
I'm interested in your critique but it seems to me you've misrepresented two of his points.
#2 compares Lisp's minimalism to any language with more complicated syntax, not just C/C++. So I don't think this insight is "common to almost all high-level languages". (The idiosyncracies he mentions are from Ruby and Python.)
#3 isn't about Visual Studio's memory usage, it's about it being slow [1]. When I work in C#, many times a day VS is unresponsive enough to break my flow, so much so that I go off and check a website like this one (it's better than sitting there feeling angry). This is disastrous in a programming tool, so I don't think the author is being precious.
(There's also a deeper point to be made here, which is that the ultra-interactiveness of Lisp and Smalltalk environments is so different from what one experiences in the likes of Visual Studio that it makes a qualitative difference in one's programming.)
There may even be a little more to #1 than you give him. "In Lisp it feels like types are a tool I can employ when I need it" refers not just to static-vs-dynamic typing but also to the fact that one can easily write functions without having to make up types to hang them on (i.e. programs don't have to be organized into object models). That's not true of all high-level languges.
I share your desire to read more knowledgeable and useful writing on this topic. But I did like the post because it's clearly coming from real experience.
[1] Admittedly, much of this slowness is due to the add-in bizarrely known as Resharper. But that's Visual Studio's fault too - for being so backward and provincial that it needs a humongous third-party workaround to achieve bare tolerability even compared to Java.
- tptacek 19y agoAddressing your points in the opposite order: #3 may be true for C# development; I read a lot of C#, but don't write it. But I did spend 4 years writing a significant amount of systems C++ code in VC++, and --- at least 8 years ago --- VC++ was significantly better than any comparable C environment. We can get into a tit-for-tat on it versus, e.g. GCC, but I feel like one way to lose a programming environment shoot-out is to imply that Microsoft half-asses that part of the business. Regarding #2, you seem to be sticking up for the author's implication that Ruby has "complex" syntax compared to Lisp. Clearly, most languages have more "idiosyncracies" (here defined as: "notation of any sort") than Lisp. That doesn't make Lisp's austerity an interesting lesson to take to other languages; it is, in fact, the major failure of Lisp. There is a notion, unaddressed in the original post but far more important than any of that post's insights, that obsessively regular syntax is crucial to metaprogramming. Even defined down to "true macros", this is simply folk wisdom: you can get "Lisp-style macros" out of any language that gives you access to an abstract syntax tree. Finally, call the two "mainstream" high level languages Ruby and Python (relegating Perl and PHP to uh, different, uh, categories). Both share the type system the author appreciates in Lisp.
- apgwoz 19y ago> it is, in fact, the major failure of Lisp. I won't even mention macros, but I'm curious as to why you think s-expressions are a failure? It's one of the things I like BEST about Lisp.
- tptacek 19y agoI like s-expressions too, but --- and I'm asserting this without a shred of evidence, appealing to the better angels of your common sense --- most developers, Peter Norvig notably included, believe other languages benefit from having more notation. For one thing, to a point, increasing the level of notational "richness" of a language improves comprehensibility of code.
- gruseom 19y agoJust curious - has Norvig said that explicitly or (like Steele and Gabriel and Weinreb and others of that generation) has he just been pragmatic?
- tptacek 19y agoI'm referring to Norvig's comments on Arc, which suggest more notation (albeit notation that remains isomorphic to sexps).
- eb 19y agoWhere/when did Norvig comment on Arc?
- tptacek 19y agohttp://www.archub.org/arcsug.txt http://www.archub.org/arcsug.txt
- abstractbill 19y ago