HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jcla1
gisp
Go2014–2022
jcla1 / gisp

gisp

Simple LISP in Go

6Distinct people
13Mentions
0Explicit recommenders
532GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Simple LISP in Go

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

No other repository is repeatedly linked in the same discussions.

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:03:16 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 year13 dated mentions

Observed mentions: 2014-01-11 14:44:27 UTC to 2022-05-08 22:52:37 UTC.

01232014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

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
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC321
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
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 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

13 sources
Nice. However, a part of my problem with jq is that changing data structure also gets awkward pretty quick. So I hoped to hijack some small Lisp that's still likely to have a suite of functional tools―`map` and such. This would also rely on the fact that I can represent JSON's maps and arrays in most such Lisps. Afaict jql doesn't have that. So far I'm planning to just fire up Hy the next time I need anything in this vein. Since it's on Python, both JSON parsing/encoding and functional stuff should be there out of the box. Alternatively, I still can try using ClojureScript with Lumo. But I don't expect too fast startup with either of them, compared to, say, Fennel/Lua. BTW, there's a Lisp that translates to Go: https://github.com/jcla1/gisp. Though not too popular, and I've heard an opinion that it's toy-like in its capabilities.
In Show HN: jql – Easier jq Alternative with a Lispy Syntax Written in Go
Interesting. The goal is "small and handy environment that mainly focusing on creating API servers or microservices". Having moved from Ruby to Go in the last year or two I'd be really interested in what language features they're pushing with that goal. I really enjoyed my work with Ruby, but I have found Golang pretty quick at these "backend" type work. On the back of this, I dug around a bit around for other transpilers to/from Golang. So far: - http://havelang.org/ - https://github.com/jcla1/gisp - https://github.com/google/grumpy (Python to Go) - https://tardisgo.github.io/ (Go to Hexe) - https://github.com/gopherjs/gopherjs (Go to JavaScript) If there are any others, be keen to find out.
In Goby: A new Ruby-inspired language written in Go
There are a number of Lisp interpreters written in Go [0-3]. There is a Lua interpreter [4]. The only compiled language I know is Gisp [5] by jcla1. I also built on top of Gisp with Gsp [6] to provide wrappers to the Go stdlib and support more standard lisp functionality. However, Kashimir is the first statically typed language implemented in Go that I have seen. The rest are dynamically typed. [0] GLISP - https://github.com/zhemao/glisp [1] golisp - https://github.com/SteelSeries/golisp [2] go-lisp - https://github.com/janne/go-lisp [3] Kakapo - https://github.com/bytbox/kakapo [4] Golua - https://github.com/akavel/goluago [5] Gisp - https://github.com/jcla1/gisp [6] Gsp - https://github.com/gsp-lang/gsp
In Kashmir: A statically typed Lispy language compiling to Go
Thank you four your reply. I had my suspicions that might be the issue (the shorthand/differences between gsp/gisp in particular). I also played a bit with the simple factorial example[f] from gisp -- which apparently doesn't work with gps(c) (gisp apparently allows calling casts as functions [eg: (int ImNotAnIntButAfloat)] -- looks like gsp chokes on that. After some tweaking I couldn't get [f] to work with gsp (but it worked fine with gisp + go build). Looks like both projects could use some more (esp. motivating) examples, and maybe a little more introduction/documentation. At least enough to encourage play :-) [f] https://github.com/jcla1/gisp/blob/master/examples/factorial...
In Show HN: A Lisp compiler and environment in Go
As far as I know, that's "regular gisp (rm $(command -v gisp); go get -u github.com/jcla1/gisp), and the full hello.go it produces is: cat hello.gsp (ns main "/fmt" "/net/http") (def hello (fn [w r] (fmt/fprintf w "hello") ())) (def main (fn [] (http/handle-func "/" hello) (http/listen-and-serve ":8080" nil))) gisp hello.gsp package main import ( "/fmt" "/net/http" ) func hello(w, r core.Any) core.Any { fmt.Fprintf(w, "hello") return nil } func main() { http.HandleFunc("/", hello) http.ListenAndServe(":8080", nil) } (Which go won't compile due to errors with imports, missing core.Any etc). I realize hn isn't the best place to discuss issues, but if anyone have played with gisp, and could
Read the rest
shed some light (eg: maybe gisp is go 1.4 only?) that'd be great. Incidentlially gsp/gspc seems to work as intended. Maybe I'm misunderstanding the purpose of gisp?
In Show HN: A Lisp compiler and environment in Go

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.