Friday Social is back! So we know we are all Lisp programmers here and we love the language and use it.
But I am sure some of us work with other languages too. Like I have to work with C, C++, Python and a number of other languages to work on different projects. I am sure some of you do too.
So the questions for this Friday Social are:
- What Lisp programming languages do you use?
- What non-Lisp programming languages do you use?
- What is your favorite Lisp programming language? Why?
- What is your favorite non-Lisp programming language? Why?
- What is that one thing about your favorite non-Lisp language that you wish to see in your favorite Lisp language?
Happy Friday!
@cadar
Nowadays I mostly use Kawa. I used to be a dedicated Guile user, for which I developed the (grand scheme) glossary, and I still use it occasionally for small things, but I’m now developing a project that relies heavily on Kawa (#GRASP).
I sometimes use Racket, especially when I need some GUI.
I also use Emacs Lisp occasionally.
I mostly use C at my day job. I also write some code in Dart and Go as well as bash scripts and makefiles. I sometimes also use Python. I also have professional experience with PHP, JavaScript, C++, C# and x86 assembly
For a long time I was very happy with Guile, especially as I was using it with my (grand scheme) glossary - it really made the language terse.
But after using Kawa, I find the lack of checked type annotations (in macroexpanded positions) really annoying. Also, I like it that Kawa provides access to Java-like OO system (that I like way more than GOOPS that comes with Guile).
I think that porting the (grand scheme) glossary to Kawa would be nice, but that would probably require some changes in the compiler.
I occasionally look at solutions to Advent of Code in various different languages, and beside my solutions in (grand scheme), I enjoy the ones in F# the most.
(They are usually quite similar in their spirit)
I also pretty much enjoy using Dart - I think that its designers are doing a great job.
I really wished that Kawa offered Dart-like object system, which in practice would mean things like mix-ins and extension methods, and more decent generics.