HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sixfootbeard
pile
Java2023–2023
sixfootbeard / pile

pile

The Pile Programming Language

2Distinct people
2Mentions
0Explicit recommenders
8GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Pile Programming Language

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: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 hour2 dated mentions

Observed mentions: 2023-09-19 00:42:06 UTC to 2023-09-19 20:08:23 UTC.

012023-09-19 00:00:00 UTC to 2023-09-19 01:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsSep 19, 00:002023-09-19 01:00:00 UTC to 2023-09-19 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 02:00:00 UTC to 2023-09-19 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 03:00:00 UTC to 2023-09-19 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 04:00:00 UTC to 2023-09-19 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 05:00:00 UTC to 2023-09-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 06:00:00 UTC to 2023-09-19 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 07:00:00 UTC to 2023-09-19 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 08:00:00 UTC to 2023-09-19 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 09:00:00 UTC to 2023-09-19 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 10:00:00 UTC to 2023-09-19 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 19, 10:002023-09-19 11:00:00 UTC to 2023-09-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 12:00:00 UTC to 2023-09-19 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 13:00:00 UTC to 2023-09-19 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 14:00:00 UTC to 2023-09-19 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 15:00:00 UTC to 2023-09-19 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 16:00:00 UTC to 2023-09-19 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 17:00:00 UTC to 2023-09-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 18:00:00 UTC to 2023-09-19 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 19:00:00 UTC to 2023-09-19 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-19 20:00:00 UTC to 2023-09-19 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 19, 20:00

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
Sep 19, 00:002023-09-19 00:00:00 UTC2023-09-19 01:00:00 UTC110
Sep 19, 01:002023-09-19 01:00:00 UTC2023-09-19 02:00:00 UTC000
Sep 19, 02:002023-09-19 02:00:00 UTC2023-09-19 03:00:00 UTC000
Sep 19, 03:002023-09-19 03:00:00 UTC2023-09-19 04:00:00 UTC000
Sep 19, 04:002023-09-19 04:00:00 UTC2023-09-19 05:00:00 UTC000
Sep 19, 05:002023-09-19 05:00:00 UTC2023-09-19 06:00:00 UTC000
Sep 19, 06:002023-09-19 06:00:00 UTC2023-09-19 07:00:00 UTC000
Sep 19, 07:002023-09-19 07:00:00 UTC2023-09-19 08:00:00 UTC000
Sep 19, 08:002023-09-19 08:00:00 UTC2023-09-19 09:00:00 UTC000
Sep 19, 09:002023-09-19 09:00:00 UTC2023-09-19 10:00:00 UTC000
Sep 19, 10:002023-09-19 10:00:00 UTC2023-09-19 11:00:00 UTC000
Sep 19, 11:002023-09-19 11:00:00 UTC2023-09-19 12:00:00 UTC000
Sep 19, 12:002023-09-19 12:00:00 UTC2023-09-19 13:00:00 UTC000
Sep 19, 13:002023-09-19 13:00:00 UTC2023-09-19 14:00:00 UTC000
Sep 19, 14:002023-09-19 14:00:00 UTC2023-09-19 15:00:00 UTC000
Sep 19, 15:002023-09-19 15:00:00 UTC2023-09-19 16:00:00 UTC000
Sep 19, 16:002023-09-19 16:00:00 UTC2023-09-19 17:00:00 UTC000
Sep 19, 17:002023-09-19 17:00:00 UTC2023-09-19 18:00:00 UTC000
Sep 19, 18:002023-09-19 18:00:00 UTC2023-09-19 19:00:00 UTC000
Sep 19, 19:002023-09-19 19:00:00 UTC2023-09-19 20:00:00 UTC000
Sep 19, 20:002023-09-19 20:00:00 UTC2023-09-19 21:00:00 UTC101

What Hacker News says

2 sources
Very interesting to see an alternative approach to implementing Clojure! And it's soooo featureful already! I was just trying to use `Path/of` in the past few days and it took awhile to get familiar with the Clojure varargs interop, so it's nice to see that pile has simple support for it already. I was also wondering how much the use of more contemporary Java features could enhance the source code or the runtime performance. This implementation seems like a great test-bed for answering such questions. A small aside: The README uses `Paths/get`, which might be deprecated eventually: https://github.com/openjdk/jdk/blob/b16e5584abcae18fdcc4494f... Should just use `Path/of` directly. BTW, I thought I would give it a try, but my initial naive attempt hasn't yielded any results: nix shell nixpkgs#maven nixpkgs#jdk20 Restored session: W
Read the rest
ed Sep 20 03:51:47 HKT 2023 pile on  master is v0.0.1-SNAPSHOT via on (ap-southeast-1) java --version openjdk 20.0.2 2023-07-18 OpenJDK Runtime Environment Zulu20.32+11-CA (build 20.0.2+9) OpenJDK 64-Bit Server VM Zulu20.32+11-CA (build 20.0.2+9, mixed mode, sharing) pile on  master is v0.0.1-SNAPSHOT via v20.0.2 on (ap-southeast-1) time ./repl [INFO] Scanning for projects... [INFO] [INFO] -------------------------< com.pile:pile-lang >------------------------- [INFO] Building pile-lang 0.0.1-SNAPSHOT [INFO] from pom.xml [INFO] --------------------------------[ jar ]--------------------------------- [INFO] [INFO] --- clean:3.2.0:clean (default-clean) @ pile-lang --- [INFO] Deleting /Users/onetom/github.com/sixfootbeard/pile/target [INFO] [INFO] --- resources:3.3.1:resources (default-resources) @ pile-lang --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 8 resources from src/main/pile to target/classes [INFO] [INFO] --- compiler:3.10.1:compile (default-compile) @ pile-lang --- [INFO] Changes detected - recompiling the module! [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent! [INFO] Compiling 294 source files to /Users/onetom/github.com/sixfootbeard/pile/target/classes [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.358 s [INFO] Finished at: 2023-09-20T03:53:30+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile) on project pile-lang: Fatal error compiling: error: release version 20 not supported -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException ./repl 2.37s user 0.18s system 236% cpu 1.075 total
In Show HN: Pile Programming Language
jhhh·Sep 19, 2023Submission

Show HN: Pile Programming Language

Pile is a Lisp running the JVM. It will feel familiar to users of Clojure as it has much of the same syntax and similar concepts, like persistent collections with literal syntax and namespaces, however no code was copied. Expected Lisp features like read/eval, macros, first-class functions and a runtime compiler have been implemented. Java interop exists including varargs support, first-class Java functions, functional interface integration and streams. Runtime polymorphism is accomplished by multimethods and generic functions (type-based multiple dispatch). I targeted the modern JVM to take advantage of features like virtual threads, invokedynamic, constantdynamic, and records to name a few. As I am still writing and testing the language there will be bugs, and the current implementation should only be used for evaluation. I am looking f
Read the rest
or feedback on the implementation and desired features people may have. Thanks!
4 points · Open discussion

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.