| ▲ | germandiago 3 days ago |
| 2934 commits OMG... huge work. |
|
| ▲ | groundzeros2015 3 days ago | parent | next [-] |
| There is just a high level of a professionalism around the whole project. Who is sponsoring all of this? Do they all work for Oracle? |
| |
|
| ▲ | andrybak 3 days ago | parent | prev | next [-] |
| The way pull requests and commits work in the OpenJDK repository -- a bot squashes each pull request into one commit: https://github.com/openjdk/jdk/pull/31120#issuecomment-51378... The final singular commit is cc278db (8389219: Implement JEP 401: Value Objects (Preview), 2026-07-31) https://github.com/openjdk/jdk/commit/cc278dbb8a1ca0754d5842... |
| |
| ▲ | fulafel 3 days ago | parent [-] | | Is there a writeup on why they choose to destroy the history? | | |
| ▲ | jerven 3 days ago | parent [-] | | You can recover the history using their tooling build on top of their bugtracker and GitHub. Specifically they capture the discussions and all small changes over time in their skara tools and are prepared to leave GitHub if needed. They had multi de adres experience and had multiple prior code repos. Still do if i understand as the Oracle team has the sun and bea code repositories pre openjdk preserved. | | |
| ▲ | fulafel 2 days ago | parent | next [-] | | Hmm. Is this about Github or Git? Dependency on Github seems tangential to treating Git as a first class record of history. edit: rereading, I guess the implication is that there's tooling built on top of Github outside of Git, so Git history is indeed not meant to be contain some things. | |
| ▲ | J-Kuhn 2 days ago | parent | prev [-] | | Before openjdk did move to github, they made sure they had a solution for those problems: * Contributors without github accounts
* Moving away from github (when needed)
* No vendor lock-in for github stuff. I personally think, this is a good idea - a lot of work, but may be worth it in the long run. |
|
|
|
|
| ▲ | thibaut_barrere 3 days ago | parent | prev | next [-] |
| Yes, massive respect for that type of perseverance on long term, important changes. |
| |
| ▲ | germandiago 3 days ago | parent [-] | | My favorite feature from Java is the same as my favorite feature from C++: pick something 10 years later or more, and it works nearly flawlessly. Also, now on the Java side: I think they made a great job avoiding async/await and using virtual threads. Amazing results. I also like all the work done around structured concurrency. |
|
|
| ▲ | estebank 3 days ago | parent | prev | next [-] |
| It's a project years in the making. |
|
| ▲ | jurgenburgen 3 days ago | parent | prev [-] |
| Seems like a horrible way to work. Why could this not have landed as a large amount of smaller PRs in a more incremental fashion, maybe Java users could have gotten some value out of it earlier. |
| |
| ▲ | DarkNova6 3 days ago | parent | next [-] | | Out of all factors this certainly isn't it. If anything, more projects could learn from the way Valhalla was handled. It started out as a highly invasive, highly disruptive and highly experimental branch that eventually turned into a beautiful specification that put semantics and performance payoff first and syntax seconds. | |
| ▲ | krzyk 3 days ago | parent | prev [-] | | This is incremental. This change is the smallest possible one that could work.
There are more coming in later. |
|
