i also consider UidFactory::createUuidV1 vs. Uuid::v1 a bit confusing. do i need to make this choice everytime?

Having (at least) three different ways to do the same thing seems excessive:

$v1 = (new UidFactory())->createUuidV1();
$v1 = Uuid::v1();
$v1 = new UuidV1();

This component was introduced as a lightweight alternative to the full-featured Ramsey library, so we may reconsider all this and simplify things if possible. Thanks!

What I didn't mention in the description is that UidFactory takes 3 constructor arguments, which allow configuring the time and entropy sources one may want to use in their app. Service configuration / DI FTW.

We could remove the static factories and the nullable constructors. That would ensure ppl always use the configurable way to create UIDs. On the other hand, this requires more code (autowiring will help a lot of course).

is a service layer really better than Ulid::generate(...): Ulid?

see just above :)

im wondering if SF should provide the service at all, in favor of invoking sources staticly where needed and/or let users design a service around it, if needed.

So, you're OK to give up the possibility to configure the source? I feel like this is a core part of UUID generation - either for tests or for clusters, being able to control how they are generated...

i was hoping default sources fit 9/10 cases yes :) though ive no real experience with it, meaning i never had to alter such sources in practice.

For simplicity i tend to lean to (considering the UUID v4 case):

$notRandom =new UuidV4('0000...');
$defaultRandom = new UuidV4();
$maybeRandom = UuidV4::generate($randomSource);

UuidV4::setDefaultRandomSource($randomSource);
$defaultMaybeRandom = new UuidV4();

considering ramsey/uuid also has a static Uuid::setFactory.

That's 2 constructors :)

PR now updated: static factories and empty constructors are removed, generator helpers are marked internal.

I'm giving up on this PR. Not worth the burden this will add on DX.
Ppl that really want to change the time and random source can inject functions in the namespace.