project-loom-comparison
Weld
| project-loom-comparison | Weld | |
|---|---|---|
| 5 | 4 | |
| 64 | 376 | |
| - | 0.5% | |
| 3.9 | 9.0 | |
| about 2 years ago | 4 days ago | |
| Java | Java | |
| MIT License | Apache License 2.0 |
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.
project-loom-comparison
-
Show HN: I finished v5 of a JVM framework I've spent spent half a decade making
Nothing to do with the project, but I read through it, so...
1. It's built natively on Jetty - very tight integration, not just some libs running in a Jetty container.
2. Web is inherently Request/Response - all of this can be handled with dramatically less resource requirements using Virtual Threads. Web is sort of the absolutely-best-use-case for Virtual Threads where as a Game Engine would be the opposite of that (one critical rendering thread and MAYBE a few extra long-lived threads for processing physics, audio, etc.)
3. I haven't tried debugging a Loom project but it's been in incubation for just under 100 years so I have to imagine this has been figured out.
4. About twice the throughput and 1/2 the latency of full OS threads - https://github.com/ebarlas/project-loom-comparison
-
What the Heck Is Project Loom for Java?
An interesting benchmark using ApacheBench on GitHub by Elliot Barlas
- Project Loom Comparison: benchmarking Java virtual threads
- Project Loom preview ships in JDK 19
- Experiment to achieve 5M persistent connections with Project Loom (Java)
Weld
-
Implement a plugin architecture
I've been using CDI for something like this. The project is temporarily hosted here.
-
Show HN: I finished v5 of a JVM framework I've spent spent half a decade making
Any DI lib would probably work, it depends on your preferences and use cases though.
I'm personally a fan of Weld since its the reference implementation of the CDI spec.
https://weld.cdi-spec.org/
- Weld 5.0.0.Beta1 released!
-
Non Spring users what are you using ??
Need only Dependency injection? Perhaps JBoss Weld, a reference CDI implementation, might interest you.
What are some alternatives?
project-loom-c5m - Experiment to achieve 5 million persistent connections with Project Loom virtual threads
Guice - Guice (pronounced 'juice') is a lightweight dependency injection framework for Java 11 and above, brought to you by Google.
greenlet - Lightweight in-process concurrent programming
Dagger2 - A fast dependency injector for Android and Java.
JDK - JDK main-line development https://openjdk.org/projects/jdk
HK2
jvm-tail-recursion - Optimizer library for tail recursive calls in Java bytecode
Apache DeltaSpike - Mirror of Apache Deltaspike
Graal - GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀
Dynamic CDI - Dynamic Context Dependency Injection
loom-benchmark
Governator - Governator is a library of extensions and utilities that enhance Google Guice to provide: classpath scanning and automatic binding, lifecycle management, configuration to field mapping, field validation and parallelized object warmup.