HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
openjdk
jdk
Java2019–2026
openjdk / jdk

jdk

JDK main-line development https://openjdk.org/projects/jdk

Languages & Compilers
Explore on GitHubRead Hacker News discussions
93Distinct people
129Mentions
0Explicit recommenders
23.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

JDK main-line development https://openjdk.org/projects/jdk

GitHub

Where it is used

No documented product use was verified in the last source check.

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:01:12 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 year129 dated mentions

Observed mentions: 2019-04-25 22:04:17 UTC to 2026-10-25 02:47:45 UTC.

01020302019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 17 mentions; 1 submissions, 16 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 17 mentions; 0 submissions, 17 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 28 mentions; 5 submissions, 23 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 22 mentions; 4 submissions, 18 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 20 mentions; 5 submissions, 15 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC707
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC606
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC17116
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC17017
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC28523
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC22418
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC12210
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC20515

What Hacker News says

28 sources
leoh·Nov 20, 2023
This is not a good argument imo. Its “rarity” still affects a tremendous number of folks in profoundly vexing ways that are difficult to debug on account of this not only affecting C but innumerable other languages’ compilers and interpreters that rely on the stock getenv implementation. I wouldn’t be surprised if a good chunk of compilers and interpreters in other languages suffer from this gotcha’. I mean, I wouldn’t even be surprised if some JVM implementations silently expose their users to bugs on account of this implementation. EDIT: … ha, sure looks like it https://github.com/openjdk/jdk/blob/a2c0fa6f9ccefd3d1b088c51...
In Setenv Is Not Thread Safe and C Doesn't Want to Fix It
gp·Nov 1, 2023
C++ lets you write anything you can imagine, and the language features and standard library often facilitate that. The committee espouses the view that they want to provide many "zero [runtime] cost," abstractions. Anybody can contribute to the language, although the committee process is often slow and can be political, each release the surface area and capability of the language gets larger. I believe Hazard Pointers are slated for C++26, and these will add a form "free later, but not quite garbage collection" to the language. There was a talk this year about using hazard pointers to implement a much faster std::shared_ptr. It's a language with incredible depth because so many different paradigms have been implemented in it, but also has many pitfalls for new and old users because there are many different ways of solving the same problem
Read the rest
. I feel that in C++, more than any other language, you need to know the actual implementation under the hood to use it effectively. This means knowing not just what the language specifies, but can occaissionally require knowing what GCC or Clang generate on your particular hardware. Many garbage collected languages are written in or have parts of their implementations in C++. See JS (https://github.com/v8/v8)and Java GC (https://github.com/openjdk/jdk/tree/36de19d4622e38b6c00644b0...) I am not an expert on Java (or C++), so if someone knows better or can add more please correct me.
In C++23: Removing garbage collection support
onetom·Sep 19, 2023
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
Joker_vD·Aug 17, 2023
> Case 2: (b == 0) || ((a == INT32_MIN) && (b == -1)) > A Java compiler, in contrast, has obligations in Case 2 and must deal with it (though in this particular case, it is likely that there won’t be runtime overhead since processors can usually provide trapping behavior for integer divide by zero). Actually, there will be runtime overhead on x86/x64: Java mandates that Integer.MinValue / (-1) evaluates to Integer.MinValue (see 15.17.2. "Division Operator /" of the Java Language Specification) but IDIV instruction raises #DE in such circumstance. So the JITter actually emits cmp eax, 0x80000000 jne .normalCase xor edx, edx cmp $reg, -1 je .specialCase .normalCase: cdq idiv $reg .specialCase: code sequence as you can see in its source ([0][1]) instead of simplistic "cd
Read the rest
q; idiv $reg": because it does not want trapping behaviour in this particular case; but e.g. AArch64 doesn't trap neither division by zero nor INT_MIN / -1. That's why accurately implementing your language's semantics on different platforms is so annoying and why C standard left itself a nice shortcut. [0] https://github.com/openjdk/jdk/blob/d27daf01d6361513a815e783... [1] https://github.com/openjdk/jdk/blob/d27daf01d6361513a815e783...
In A Guide to Undefined Behavior in C and C++ (2010)

Showing the 15 most recent of 28 sources. Enable JavaScript to search and browse every indexed mention.

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.