#20 - Emacs Lisp
#24 - Clojure
#25 - Racket
#35 - Scheme
#36 - Common Lisp
Interestingly, had PLT Scheme not been renamed into Racket, Scheme would probably be the most popular Lisp on Github.
11–20 of 25 posts
#20 - Emacs Lisp
#24 - Clojure
#25 - Racket
#35 - Scheme
#36 - Common Lisp
Interestingly, had PLT Scheme not been renamed into Racket, Scheme would probably be the most popular Lisp on Github.
Because they predate Github by many years Lisps tend to have already established other repositories. That's not to say that Lisp is popular, only to suggest that Github is not necessarily the best sampling of its development communities.
Because they predate Github by many years Lisps tend to have already established other repositories. That's not to say that Lisp is popular, only to suggest that Github is not necessarily the best sampling of its development communities.
I also suspect that Github might be a terrible sample of the overall programming community. I'd be curious to find out what the real numbers are if we also take in consideration the large corp, gov and science conglomerates who might be using anything form COBOL to Ada.
Lisp is probably never going to get huge and that's ok. It's a niche language for a subset of the programming community that has a specific set of values, and not everybody needs to or wants to share them. Obviously lisp users think you're missing out if you're not using a lisp, and will help you out as much as possible if you decide to join the so called renaissance. However I think the community understands that it…
You could, of course, program in a more functional style in Lisp (and that style is encouraged more in some Lisps than others), but you're not forced to.
Earlier quoted context omitted.
I also suspect that Github might be a terrible sample of the overall programming community. I'd be curious to find out what the real numbers are if we also take in consideration the large corp, gov and science conglomerates who might be using anything form COBOL to Ada.
Large corporations, governments and science conglomerates that use COBOL and Ada are not part of any community.
Lisp is probably never going to get huge and that's ok. It's a niche language for a subset of the programming community that has a specific set of values, and not everybody needs to or wants to share them. Obviously lisp users think you're missing out if you're not using a lisp, and will help you out as much as possible if you decide to join the so called renaissance. However I think the community understands that it…
Minor nitpick: Lisp is not a purely functional language. It's a multi-paradigm language. You could, of course, program in a more functional style in Lisp (and that style is encouraged more in some Lisps than others), but you're not forced to.
Because they predate Github by many years Lisps tend to have already established other repositories. That's not to say that Lisp is popular, only to suggest that Github is not necessarily the best sampling of its development communities.
Citation needed. Because I see C and C++ in there, that also predate GitHub by many years.
And since we're not talking about 50 year old Lisp programmers (that would predate GitHub for 3 decades), so does Perl, Python, Java etc.
Because they predate Github by many years Lisps tend to have already established other repositories. That's not to say that Lisp is popular, only to suggest that Github is not necessarily the best sampling of its development communities.
> Because they predate Github by many years Lisps tend to have already established other repositories. Citation needed. Because I see C and C++ in there, that also predate GitHub by many years. And since we're not talking about 50 year old Lisp programmers (that would predate GitHub for 3 decades), so does Perl, Python, Java etc.