HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
fukamachi
ningle
Common Lisp2012–2019
fukamachi / ningle

ningle

Super micro framework for Common Lisp

5Distinct people
5Mentions
0Explicit recommenders
301GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Super micro framework for Common Lisp

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2012-11-15 08:57:01 UTC to 2019-06-22 04:27:35 UTC.

0122012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC202
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

What Hacker News says

5 sources
Roswell comes to mind for application building and distro management. Add in ningle for web app building and woo for the server (the benchmarks are really good), and you're basically good to go. I think the main problem is there's too many implementations of the same thing in CL, so devs basically have to agree on a very specific subset of tools for every project, which adds a fair bit of overhead. https://roswell.github.io/ https://github.com/fukamachi/woo https://github.com/fukamachi/ningle p.s. Not the author, but a big fan.
In The Tragedy of the Common Lisp: Why Large Languages Explode
Lisp Programmer here, - quicklisp is the default for package management. If you need to load a different version of a package you can use the local projects dir. I've never used Qi before, so I really can't say anything on it. - For a framework I would recommend either Clack[1] (relatively small but featureful) or Ningle[2] (micro-framework).Both support multiple backends including Huntchentoot. - There are object store databases and serializers like cl-store and cl-prevalence, but if you really want to take full advantage of Lisp I would recommend you use hash tables and reader macros. There's also plenty of mature (by lisp standards anyway) SQL APIs and ORMs like postmodern[3]. - For hosting I use AWS, haven't used anything else so can't say much on it. [1] https://github.com/fukamachi/clack [2] https://github.com/fukamachi/ningle [3]
Read the rest
In Ask HN: Learning Lisp, and I have some questions
Framework: Caveman2[0] or Ningle[1], which run on Clack[2] (like Rack/WSGI), which supports five backend servers. Templates: Djula[3], closure-template[4]. ORM: Crane[5], Postmodern[6]. [0] https://github.com/fukamachi/caveman [1] https://github.com/fukamachi/ningle [2] https://github.com/fukamachi/clack [3] https://github.com/mmontone/djula [4] https://github.com/archimag/cl-closure-template [5] https://github.com/eudoxia0/crane [6] http://marijnhaverbeke.nl/postmodern/
In Why Racket? Why Lisp?
"The most popular web server for CL, Hunchentoot hasn't been touched (based on the darcs repo anyway) since Tue, 24 Aug 2010." That statement is just untrue, take a look yourself. https://github.com/edicl/hunchentoot/commits/master Also there is an active community in Japan from what I can gather from github.com They done cl-annot[1], which is a way to annotate functions with the @ syntax from python. Clack[2], the WSGI-equivalent for cl. And the Caveman[3] and Ningle[4] webframeworks. [1]: https://github.com/arielnetworks/cl-annot [2]: https://github.com/fukamachi/clack [3]: https://github.com/fukamachi/caveman [4]: https://github.com/fukamachi/ningle
In Mocl: Common Lisp for iPhone/iOS, Android, and other mobile platforms
The announcement speaks as if web applications in Common Lisp was itself a solved problem. The community surrounding that isn't exactly vibrant. An example from an attempt to find a viable/nice Common Lisp templating library for making web apps (a problem for me before, I hate CL-WHO. Vile.) http://www.cl-user.net/asp/U5Hd/sdataQGW2OvQLz758DQdX8yMX8yB... Hrm. Yes. Hrm. Seems promising, exceeeept... https://groups.google.com/group/cl-terrace/web/djula The Google Group for it has...disappeared? http://common-lisp.net/project/bpm/darcs/djula/ Yay, code! That hasn't been touched since 2008! CL-WHO, which I think is the most popular way to solve this problem hasn't been touched in 2 to 7 months, depending on how you measure it. See here: https://github.com/edicl/cl-who The Ningle web framework for Clack, found here: https://github.com/fukamach
Read the rest
i/ningle Not been touched in 4-8 months. Caveman (clack framework): https://github.com/fukamachi/caveman/ 4-8 months. HTML-TEMPLATE hasn't been touched since Tue, 02 Dec 2008. The most popular web server for CL, Hunchentoot hasn't been touched (based on the darcs repo anyway) since Tue, 24 Aug 2010. Take a look for yourself: http://common-lisp.net/~loliveira/ediware/ The Common Lisp community is moribund at best. I would PREFER to use Common Lisp over, say, Clojure or Python however the fact is that there just aren't enough people using it or maintaining web development software for it to overcome the time expenditure trade-offs. So, can we drop the triumphant tone as it concerns CL? Even Paul Graham tells most people to just use Clojure.
In Mocl: Common Lisp for iPhone/iOS, Android, and other mobile platforms

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.