Scrutor VS loom

You can with MS's default DI as well via scrutor.

if you are heavily invested in autofac you can replace the build in DI with another container. at this point i don't think it is that necessary. especially if you use scrutor. it gives your some nice assembly scanning registration that autofac/simple injector give https://github.com/khellang/Scrutor

If you wouldn't mind, I have one additional question. If I wouldn't bother to remove this loading, how could one add that as service when using DI? I have found tool called Scrutor (https://github.com/khellang/Scrutor), is it something commonly used in situation like this?

I much prefer using Scrutor and asbly scanning myself. https://github.com/khellang/Scrutor

you can also use Scrutor to get closer to Autofac functionality https://github.com/khellang/Scrutor

That can't be the only justification, because you can easily register services using reflection without using MediatR.

I might suggest additional registration time extensions to modify the behavior as needed on classes. Take a look at Scrutor for some inspiration on API specifically.

There is a package that simplifies it for you if you want. But not everybody agrees that automatic registration is good pattern, so you have a choice.

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.

Loom is actively developed https://github.com/openjdk/loom

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.

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.

https://github.com/openjdk/loom/blob/fibers/src/java.base/share/classes/sun/nio/ch/NioSocketImpl.java#L177

[1] https://github.com/openjdk/loom/blob/fibers/src/java.base/share/classes/java/lang/VirtualThread.java#L933