Jimmy Shen

The sortable point from @gpetretto is pretty important. Some of the more complex workflows in emmet require the IDs to be sorted (ideally based on creating time). So if we...

Maybe just use UUID1 for now, and when we add the support for UUIDS in emmet we can write it with both UUID1 and UUID7 in mind.

OK!

Ditto @janosh and @gpetretto on the size thing. since the UUID bit of code in jobflow is so small can't we just move it all to emmet core?

I think we can just geta PR going with UUID1 for now and add others later.

I agree with the naming issue, and a change to `uid` is probably needed. I think we can enable support for multiple id types, keep it at `uuid4` as default...

So things on both emmet and jobflow are kept flexible for the time being and the default behavior is basically "nothing changes" but if you want to use ULID or...