3 ms·
While you are, in general, in agreement with my original comment, I'm going to push back a little bit. > Mathematica understands that concrete syntax is not ab
by aidenn0 4y ago
While you are, in general, in agreement with my original comment, I'm going to push back a little bit.
> Mathematica understands that concrete syntax is not abstract syntax, the former can be (indeed, needs to be in a high level language) rich and expressive, the latter can be spartan and pure.
While there are plenty of novice Lispers who don't understand this about syntax, the balance of the lisp community does, and most of them are still perfectly happy with the (relatively) tight coupling between the concrete and abstract syntax. People who are unhappy with it tend to either write reader macros or invent Julia [edit] I neglected to mention Racket language modules here as well.
> - Dynamicity:
> - Image-Based Development:
Dynamicity and image based development go somewhat hand-in-hand. Being able to e.g. safely redefine a class at runtime is certainly less important with out it. There is also a certain je ne sais quoi of the combination of dynamicity, native compiler, and tooling. I can redefine a function and collect assembly-level profiling of it without restarting the program. As far as I know there's nothing preventing someone from implementing Ruby in such a way as to allow this, but here we are.
Smalltalk and Lisp developed in parallel, with lots of cross-pollination, so there is a lot of overlap there; in turn Erlang was heavily inspired by Smalltalk.
> - The Condition System: ...it's also only in Common Lisp,
- Dylan
- Scheme: prior to R6RS this was left to the implementation; the R6RS exception specification is certainly similar to CL's in feel (but it uses explicit continuations, which is more scheme like)
> Lispers need to wake up to the fact that Lisp is not special in 2020. They needed to wake up to that fact since 2000, but better late than never I guess.
I think Lisp is at least special still in the sense that its particular combination of features are in some ways unique. I also think that in 2000 (and even more so in 1995), it conformed to some much stronger definition of special in terms of having some features that were either rare, or not present at all, in other non-experimental languages.
- Banana699 4y agoAll of your points are fair, convincing and well-taken. I'm (much much) softer on lisp than my somewhat aggressive reply would imply; Scheme, Clojure and Common Lisp (in that order, according to me) are all amazing languages that contributed significantly to PL design and implementation. Racket in particular is extremly high up the list, with its amazing "Language As A Library" attitude that shocks and excites me very much. What gets me is just the smug attitude of "Hehe, look at all those uncultured masses developing in a language other than our lord and savior. <shouts loudly> We were there since 1960, swines <shakes fists>." When I say that lisp is "not special", I don't mean it's bland or uninteresting in the sense of Java-The-Language (not the VM), that would be a contradiction since I already acknowledged the uniqueness of the condition system and the Image-Based tools, and the interestingness (but not uniqueness) of macros and CLOS. I just mean it in the "not specially special" sense, i.e. it's not any more special than Erlang, Smalltalk, Haskell, OCaml, Perl, or any of the dozen or so languages that led the way in the development of new abstractions and ways of expression. It's a bit like saying "Greece isn't special" or "India isn't special" to a modern nationalist of those countries who think that their civilizations are unmatched. Yes, Greece and India are very special cultures who invented fantastic things and led the way in many ways, but so is Egypt, Iraq, China, Western Europe, Russia, US, etc... While you're perfectly fine being proud of things you love ("Smalltalk invented OOP!", "Erlang invented concurrency!"), denigrating other things and implying that they're posers who can't possibly match the thing you like despite their "reinvention" is off course something that will get people riled up and understandably aggressive.
- rramadass 4y ago>in turn Erlang was heavily inspired by Smalltalk. That is not correct. Joe Armstrong in his paper The Development of Erlang says this; The design of Erlang was heavily influenced by ideas from the logic and functional programming communities. Other sources of inspiration came from languages such as Chill and Ada which are used in industry for programming control systems. We concluded that we would like something like Prolog with added facilities for concurrency and improved error handling. No such language existed at the time. By about 1988 is was clear that Erlang as it was now called was a good language for prototyping telephone exchanges [10]. It was a strange mixture, with declarative features (inherited from Prolog), multi-tasking and concurrency (inherited from EriPascal and Ada) and an original combination of error handling mechanisms.