addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Ritchie C.


Waco, TX

Member since:

April 27, 2014

What interests you in Lisp

simplicity, expressiveness and flexibility

Have you programmed in any Lisp based language before?

I was using common lisp for my side projects. Lately started using clojure for it's concurrency and varieties of libraries. And of course, elisp for all the emacs stuffs ;)

Strong typing or dynamic typing?

Can I have both? Generally I would go with dynamic typing, but I would like to have strong typing available when I start to tweak for performance. Common Lisp, for example, can do both.

Have you heard of Multi-methods?

Yes, in many different terms. It's Clojure's way of saying dynamic dispatch. C++ virtual function, CLOS' generic function are all dynamic dispatch implemented in different ways. They are all equivalent to multi-method.

Relational, Object Oriented, Graph, Network, Hierarchical databases. Which is your favorite and why?

Among these, I only have experience with relational db, but I generally prefer nosql for it's flexibility and scalability.


(defmacro procrastinate [work] `(fn [] ~work))

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy