ea-async
Quasar
ea-async | Quasar | |
---|---|---|
4 | 6 | |
1,362 | 4,548 | |
0.2% | 0.2% | |
0.0 | 0.0 | |
about 2 years ago | 3 months ago | |
Java | Java | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
ea-async
-
Fluent: Static Extension Methods for Java
I feel like this misses the reason I like extension methods: discoverability.
With an extension method, I can do `object.` and my IDE will tell me what can be called on object. With a static helper method, it isn't as easy to know what is available. I need to know which helpers actually exist.
Since this doesn't have IDE support, it doesn't help discoverability. I'm not going to get nice autocomplete that shows me what is available. In fact, my IDE is going to highlight it as a bug. If I have a spelling mistake, I won't be able to easily pick it up - I'll assume it's just the normal complaint for all of these fluent extension methods.
That makes this simply syntactic sugar rather than something that actually helps me discover things more easily. It then hurts readability and navigation since I can't easily click through to get the definition of the method.
On a more general note about Java, things like this are one of the reasons I don't love the Java ecosystem. People try to change the behavior of Java in really hacky ways that don't work well. I understand that it's an attempt to overcome shortcomings in the language, but when one looks other languages it becomes clear that Java could have just evolved the language to be better. Java has lots of good things and I'm not looking to argue that. However, when I look at things like this, it makes me think that Java needs to really address the core language.
Instead, we get lots of tools like this which might be nice, but make it really hard to understand what's going on. Electronic Arts created an async/await library that'll do crazy stuff to let you do async/await style programming (https://github.com/electronicarts/ea-async). Yes, Java is doing good things with structured concurrency and Project Loom, but the point is how people keep trying to work around the language. There are so many POJO generators it isn't funny: AutoValue, Immutables, JodaBeans, Lombok, and more I'm probably forgetting. Java records don't fulfill everything (and they're at least a decade late). Java doesn't support expression trees for lambdas so libraries sometimes do crazy hacky things to make that exist.
Java is a great piece of technology, but it feels like people are often trying to overcome issues with the language through really hacky means in a way that I don't see in other languages. Java is getting better about modernizing the language, but it still feels like people are running against the language more than in other ecosystems.
-
What are some forbidden, broken, possibly even black magic stuff that you can do in Java and to that extent, JVM in general?
https://github.com/electronicarts/ea-async via preprocessing the bytecode in the jar or at start time
-
Concrete reasons why one would choose java over node.js?
Like I mentioned in the other comment - EA Async can help there, it brings async-await semantics to CompletableFutures and resilience4j has CompletableFuture decorators that you can apply to get retries, circuit-breakers and all the good stuff they offer.
- Async await in Java
Quasar
-
Java 21 makes me like Java again
Java 21 doesn't retrofit green threads though. Quasar [0] is a library that implemented fibers for Java and the main developer pron has joined the OpenJDK development team. All that was necessary for first party support is to make the JDK libraries yield when blocking.
Adopting async isn't impossible at all, there is very little demand for it.
[0] https://docs.paralleluniverse.co/quasar/
-
Lies we tell ourselves to keep using Golang
Third party options have been around for nearly a decade now: https://docs.paralleluniverse.co/quasar/
-
Picking up Go as a Java dev—what could possibly go wrong?
Quasar Fiber (https://docs.paralleluniverse.co/quasar/) is the equivalent implementation of goroutine in Java.
-
Helidon Nima - First Framework built from the ground up for Project Loom
Even Loom architect Ron Pressler had something else in mind with his earlier prototype Quasar, with a spaceship demo.
- Thread Pools on the JVM
-
DoorDash: Migrating From Python to Kotlin for Our Backend Services
I'd say because of Erlang. Loom's architect was building a bytecode-modifying (with a javaagent) lib named Quasar before he joined Oracle. The project page mentions a news titled "Introductory blog post: Erlang (and Go) in Clojure (and Java), Lightweight Threads, Channels and Actors for the JVM." in May 2, 2013.
What are some alternatives?
Reactive Streams - Reactive Streams Specification for the JVM
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
navigo - A simple vanilla JavaScript router.
Apache ZooKeeper - Apache ZooKeeper
CreepyCodeCollection - A Nonsense Collection of Disgusting Codes
Zuul - Zuul is a gateway service that provides dynamic routing, monitoring, resiliency, security, and more.
Apache Storm - Apache Storm
kotlin - The Kotlin Programming Language.
Orbit - Orbit - Virtual actor framework for building distributed systems