picrin

lightweight scheme interpreter

2Distinct people

2Mentions

0Explicit recommenders

422GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

lightweight scheme interpreter

GitHub

No documented product use has been verified yet.

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.

No other repository is repeatedly linked in the same discussions.

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.

HN mentions by month2 dated mentions

Observed mentions: 2016-01-30 20:54:44 UTC to 2016-10-07 13:40:51 UTC.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Jan 2016	2016-01-01 00:00:00 UTC	2016-02-01 00:00:00 UTC	1	1	0
Feb 2016	2016-02-01 00:00:00 UTC	2016-03-01 00:00:00 UTC	0	0	0
Mar 2016	2016-03-01 00:00:00 UTC	2016-04-01 00:00:00 UTC	0	0	0
Apr 2016	2016-04-01 00:00:00 UTC	2016-05-01 00:00:00 UTC	0	0	0
May 2016	2016-05-01 00:00:00 UTC	2016-06-01 00:00:00 UTC	0	0	0
Jun 2016	2016-06-01 00:00:00 UTC	2016-07-01 00:00:00 UTC	0	0	0
Jul 2016	2016-07-01 00:00:00 UTC	2016-08-01 00:00:00 UTC	0	0	0
Aug 2016	2016-08-01 00:00:00 UTC	2016-09-01 00:00:00 UTC	0	0	0
Sep 2016	2016-09-01 00:00:00 UTC	2016-10-01 00:00:00 UTC	0	0	0
Oct 2016	2016-10-01 00:00:00 UTC	2016-11-01 00:00:00 UTC	1	0	1

2 sources

SBCL really isn't that slow [0], being on par if not faster than Java in most things. Python is a magnitude of order slower [1] than most things, and that was my point. newLISP is slow. I do have to take exception to you calling interpreted slow - because you've called Python interpreted, I'm guessing bytecode interpreted fits your view. Picrin [2] is bytecode interpreted, and isn't slow. [3] By Rebol I mostly meant Red, which isn't exactly slow, as it aims for 1-3x the speed of C. (Though I can't find any decent set of benchmarks for it currently). [0] https://benchmarksgame.alioth.debian.org/u64q/lisp.html [1] http://benchmarksgame.alioth.debian.org/u64q/python.html [2] https://github.com/picrin-scheme/picrin [3] http://www.larcenists.org/benchmarksGenuineR7Linux.html