Quasar
Orbit
Our great sponsors
| Quasar | Orbit | |
|---|---|---|
| 6 | 2 | |
| 4,547 | 1,705 | |
| 0.2% | 0.6% | |
| 0.0 | 0.0 | |
| 3 months ago | almost 3 years ago | |
| Java | Kotlin | |
| GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
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.
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.
Orbit
-
Actor system for the JVM developed by Electronic Arts
> I can't help but recoil from a "hello world" that pulls in an entire container ship of dependencies.
Where do you see the list of dependencies? Seems to me to be the ones defined at https://github.com/orbit/orbit/blob/233956001f1206ccbfde72ef..., is that correct? Doesn't look like "an entire container ship" but maybe the NPM madness have ruined me.
> Especially that we already have a perfectly good, battle-hardened, and relatively lightweight implementation of Actor model with Erlang / Elixir.
Yeah, if you're already using Erland or Elixir, why don't you go with that instead? This seems to be for the JVM, so one could assume that the ones who want to use this, is already invested heavily in the JVM ecosystem (which as far as I know, EA is when it comes to backend servers).
- About Halo game's backend
What are some alternatives?
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
Lagom - Reactive Microservices for the JVM
Apache ZooKeeper - Apache ZooKeeper
Zuul - Zuul is a gateway service that provides dynamic routing, monitoring, resiliency, security, and more.
JGroups - The JGroups project
Apache Storm - Apache Storm
kite - Lightweight service-based PubSub, RPC and public APIs in Java
Pinpoint - APM, (Application Performance Management) tool for large-scale distributed systems.
Bt - BitTorrent library and client with DHT, magnet links, encryption and more