loom
JDK
Our great sponsors
loom | JDK | |
---|---|---|
10 | 190 | |
1,824 | 18,352 | |
1.0% | 2.1% | |
10.0 | 10.0 | |
4 days ago | 2 days ago | |
Java | Java | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
loom
-
Using Java's Project Loom to build more reliable distributed systems
It's more accurate to say Loom is [a particular type of] continuations in the JVM, which can be used to implement green threads / fibers.
You can see the implementation of VirtualThread here: https://github.com/openjdk/loom/blob/fibers/src/java.base/sh...
This uses the internal 'one-shot delimited continuation': https://github.com/openjdk/loom/blob/fibers/src/java.base/sh...
So, at least in principle, there is scope for other styles of concurrency to be implemented over this.
- Virtual thread (along with Structured concurrency and Scope Local) is previewing in JDK19?
-
6 .NET Myths Dispelled — Celebrating (Almost) 21 Years of .NET
Loom is actively developed https://github.com/openjdk/loom
- Project Valhalla status summary
-
Brian Goetz: "I think Project Loom is going to kill Reactive Programming"
Currently the Thread public constructor defaults to platform threads to be fully backwards compatible. So all libraries must be updated to support the new model.
-
Java’s Project Loom, Virtual Threads and Structured Concurrency with Ron Pressler
I've been casually following the repo ( https://github.com/openjdk/loom ) and the mailing list ( https://mail.openjdk.java.net/mailman/listinfo/loom-dev ) over the last 18 months or so, and it definitely appears that things are ramping up as of late. The implication (as I see it) is that they are relatively happy with the general design are and are at the point where they want help from experts in the various areas of the JDK (GC, Debugging, etc) to make sure that their pieces play well with Loom.
-
[Project Loom] New ea build based on jdk-17+13 is available for download.
https://github.com/openjdk/loom/blob/fibers/src/java.base/share/classes/sun/nio/ch/NioSocketImpl.java#L177
- [project loom] New thread builder API.
-
Have created a short and practical intro into what project loom is all about.
[1] https://github.com/openjdk/loom/blob/fibers/src/java.base/share/classes/java/lang/VirtualThread.java#L933
- Loom adds a feature to generate thread dump in JSON format.
JDK
-
Java 23: The New Features Are Officially Announced
Completely gutted from the OpenJDK, last I checked. See here for the culprit PR: https://github.com/openjdk/jdk/pull/18688
-
macOS 14.4 might break Java on your machine
> Yes, they're changing one aspect of signal handler use to work around this problem. They're not stopping the use of signal handlers in general. Hotspot continues to use signals for efficiency in general. See https://github.com/openjdk/jdk/blob/9059727df135dc90311bd476...
This whole thread is about SIGSEGV, and specifically their SIGSEGV handling. However, catching normal signals is not about efficiency.
Some of their exception handling is still odd: There is no reason for a program that receives SIGILL to ever attempt continuing. But others is fine, like catching SIGFPE to just forward an exception to the calling code.
(Sure, you could construct an argument to say that this is for efficiency if you considered the alternative to be implementing floating point in software so that all exceptions exist in user-space, but hardware floating point is the norm and such alternative would be wholly unreasonable.)
> The wonderful thing about choosing not to care about facts is having whatever opinions you want.
I appreciate the irony of you making such statement, proudly thinking that your opinion equals fact, and therefore any other opinion is not.
This discussion is nothing but subjective opinion vs. subjective opinion. Facts are (hopefully, as I can only speak for myself) inputs to both our opinions, but no opinion about "good" or "bad", "nasty" or not can ever be objective. Objective code quality does not exist.
-
The Return of the Frame Pointers
I remember talking to Brendan about the PreserveFramePointer patch during my first months at Netflix in 2015. As of JDK 21, unfortunately it is no longer a general purpose solution for the JVM, because it prevents a fast path being taken for stack thawing for virtual threads: https://github.com/openjdk/jdk/blob/d32ce65781c1d7815a69ceac...
- JDK-8180450: secondary_super_cache does not scale well
- The One Billion Row Challenge
- AVX2 intrinsics for Arrays.sort methods (int, float arrays)
- A gentle introduction to two's complement
-
Java JEP 461: Stream Gatherers
Map doesn't implement the Collection interface.
https://github.com/openjdk/jdk/blob/master/src/java.base/sha...
-
C++23: Removing garbage collection support
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.
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.
- Make Immutable Maps ValueBased
What are some alternatives?
MQTTnet - MQTTnet is a high performance .NET library for MQTT based communication. It provides a MQTT client and a MQTT server (broker). The implementation is based on the documentation from http://mqtt.org/.
Graal - GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀
cats - Lightweight, modular, and extensible library for functional programming.
aircraft - The A32NX & A380X Project are community driven open source projects to create free Airbus aircraft in Microsoft Flight Simulator that are as close to reality as possible.
rpi-projects - Drivers and home automation projects for Raspberry PI.
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
csharplang - The official repo for the design of the C# programming language
steam-runtime - A runtime environment for Steam applications
coyote - Coyote is a library and tool for testing concurrent C# code and deterministically reproducing bugs.
intellij-community - IntelliJ IDEA Community Edition & IntelliJ Platform
lucene-grep - Grep-like utility based on Lucene Monitor compiled with GraalVM native-image
kitten - A statically typed concatenative systems programming language.