You forgot about distribution, poor db performance and predictability.
I would recommend staying away from any uuid <= v4
UUIDv1 is ever worst as it leaks data. stay away from it!
It's all captured in my research.
uuid v4 is a very weak uuid format
- it will generate collisions when distributes
- it doesn't store well as an indexed column
- crypto can be unsecure for some implementation
I wrote an article at
https://medium.com/@orefalo_66733/globally-unique-identifier-a-fair-comparison-12b114c78ead
a reason for Tailwind?
It's quite simple: not everyone is an expert at broken CSS, and spending hours trying to understand its layouts is not an option.
Tailwind also provides a different approach to styling - the right approach IMHO
I think they should have pushed it further and not write anything on disk - this would make it even faster...
Or better, not even read the original sources!
Neat piece of logic and very nice full featured UIs.
If I may,
- what is the roadmap for this project?
- How does it relate to https://github.com/paed01/bpmn-engine
Sincerely
Why is it "better"?
Is it functionality? -> need details
Is it performance? -> need benchmarks
Is it cost of ownership? -> need cost/expense analysis
Come one guys, plz don't be so geeky. think in multiple dimensions.