HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dyoo
whalesong
Racket2014–2017
dyoo / whalesong

whalesong

Whalesong: Racket to JavaScript compiler

3Distinct people
3Mentions
0Explicit recommenders
251GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Whalesong: Racket to JavaScript compiler

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, 5:04:57 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 year3 dated mentions

Observed mentions: 2014-09-24 22:56:17 UTC to 2017-08-23 21:28:52 UTC.

012014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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 comments2017

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 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
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

What Hacker News says

3 sources
If anyone does not recognize dyoo, the owner of hashcollision.org is also the author of Whalesong, a Racket->Javascript system. I think it has been discussed before on HN. https://github.com/dyoo/whalesong Needless to say, if this guy is fudging Racket, I am not sure what we can say about the rest of us and what we do with the language. Haha. EDIT: Was the author, it seems he passed it off to another Racketer now that he is busy with other stuff. Should have clicked the link before posting. https://github.com/soegaard/whalesong
In F*dging up a Racket
I agree that Clojure is continuing to rapidly gain mind share – among long-time Lispers, relative newcomers to programming, and also seasoned "curly bracers" that a few years ago never thought they'd see a day when Lisp would make it into mainstream dev shops. Personally, I like it a lot and use it on a daily basis. The excitement around it is in no small part due to the insightfulness and ongoing hard work of Rich Hickey[1], his close collaborators at Cognitect[2], and some amazingly dedicated community talent (e.g. Philip Hagelberg[3]). Not to be overlooked is the brilliant decision to have it be a "hosted language" that interoperates with non-Clojure code on the JVM with little to no hassle – that opens a lot of doors, better believe it! That being said, I attended RacketCon 2014[4] last Saturday and was blown away by the work going on
Read the rest
in that community. Michael Fogus[5], a well-known name in the Clojure community, even gave the keynote[6]. The language's creator, Prof. Matthias Felleisen[7], and his grad students have been doing truly cutting-edge work over the last 18+ years (what became Racket was "conceived" at Rice University in Fall 1995). It's a fair question, though, whether the Racket team even wants the language to "make it big," i.e. along the lines of Clojure's rapid rise in popularity. I got the impression they have mixed feelings about that prospect, and those concerns have certainly shaped (and will shape) their marketing of Racket. My thought is that if, in the next couple of years, they are able to achieve a really good compile-to-JS story (some work has been done already[8]) and a solid JVM-hosted implementation, then they may get a bunch of spill-over from the Clojure community without even trying to "steal sheep". There are some tremendously powerful language-level facilities already built into Racket that will likely not be implemented in Clojure any time in the foreseeable future, e.g. delimited continuations[9]. Also, the Racket team seems to have the right mind about learning from other languages, e.g. picking up some of the popular idioms from Clojure. So, all in all, I think Lisp's legacy is far from definitive and it will be truly exciting to see what comes out of the Clojure and Racket camps over the next 5 years or so! [1] https://twitter.com/richhickey [2] http://cognitect.com/ [3] https://github.com/technomancy/ [4] http://con.racket-lang.org/ [5] http://blog.fogus.me/ [6] https://www.youtube.com/watch?v=oe2tK5Lxybc [7] http://en.wikipedia.org/wiki/Matthias_Felleisen [8] https://github.com/dyoo/whalesong [9] http://docs.racket-lang.org/guide/conts.html
In The Legacy of Lisp (2005) [pdf]

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.