ZIO VS Vert.x

The first point is about a fucking conference in 2016, in which the organizer invited several people with a process (and thoughts) explained here https://degoes.net/articles/lambdaconf-controversy aimed at being blind to sex/religion/political views etc. He repeatedly stated to be in a strong disagreement with "white supremacist" views and the such. The first words of the ZIO's code of conduct are precisely about that btw https://github.com/zio/zio/blob/master/docs/about/code_of_conduct.md, and zio follows the scala code of conduct. You can agree or disagree about whether "allowing that person, selected in the way described above (without any preference at all for white supremacists of course), to speak precisely about one particular topic and only if they adhere to the code of conduct" is "giving them a platform to share their ideas", but even if you do think that the first approach is completely wrong, it's a pretty big jump from here to accuse the person holding that view (actually a less-strong version of it) of being a white supremacist themselves and the same of all people that associate with that person (the organizer) and stalk and harass them for years on end

Since you are talking about an IO monad, maybe ZIO (https://zio.dev/) offers some interesting ideas. Rather than an IO monad, ZIO is a family of IO monads with type parameters to support user-defined environments and error types.

ZIO (interoperates with TypeLevel to some extent)

please show me something like this: https://akka.io/ or this: https://zio.dev/ or this: https://github.com/milessabin/shapeless

Here is link number 1 - Previous text "ZIO"

Nothing like cats or ZIO for Kotlin. I do hope I don't have to explain why Kotlin Arrow is not a good replacement.

ZIO on the other hand doesn't rely on those concepts, so I guess it could be possible ? But I'm not too sure the code would look great without Scala's for-comprehensions and there may be other blockers... By the way there's been some work done in ZIO to provide a Java facade : https://github.com/zio/zio/pull/383. Not sure the interop on that would work so great tbh.

That being said, between the two you mentioned, spring is probably the more popular framework because of the magic annotation processing it provides if you're into that. Otherwise vertx seems like a good framework if you want something light, not sure which large projects are using it out there though short of looking at their site.

Something like Vert.x would be much close to node.js (it's inspired by it!) and it's pretty easy to use. I would also at least read about the following frameworks before deciding on which one to try a bit more:

Because the developers of Quarkus also worked on Vert.x, the former also offers a plugin that integrates the latter. Vert.x is full reactive and provides the concept of routes. With Quarkus, you can annotate methods to mark them as routes. One can migrate the above code to routes:

Backend newb, here. I have a dumb question - can someone give me a summary, or blog post to a summary, of the pros /cons of async versus threads?

One thing I have been using as a way of understanding hi-perf backends is analyzing why the vert.x framework [1] (and its underlying server, netty) does so well on benchmarks [2], but as newb, I do not think I would get a lot form that exercise without a little hand holding.

[1] https://vertx.io/

[2] Ad of today, #28 on tech empower benchmarks - https://www.techempower.com/benchmarks/

Came here to say this. Vert.x was inspired by Node+Express. It was even originally named NodeX.

Vert.x

Check out ES4X. It's JS and TS bindings for GraalJS for Vert.x. Vert.x is the basis for Quarkus, so this is definitely possible.

I've been working with the Vert.x framework for more than 4 years but I won't stop being excited how simple, lightweight and elegant it is (especially the event loop thread model). In this blog post I will tell you how we implemented PeriodicallyExpiringHashMap data structure in less than 100 lines of code. But first let me give you a bit of a context about why do we need it.

You might want to consider a lightweight reactive library like Akka or Vert.x which will make more efficient use of threads, and takes the work away of having to write a concurrent, distributed application, so you can just focus on writing your poker app.