Why it would be better to get rid of time_machine

[JulianKowalczuk]

So... You use time_machine for datetime usage purpose. I see pros of usage it, but...

1. time_machine is forbidden by its author. Many PRs with 0 replies, there is no repo activity for MONTHS (even in other projects). Since Your package relies on it, all bugs from time_machine breaks Your package also :/

2. [Web] Get stuck at initialize call Dana-Ferguson/time_machine#27
   This one breaks production build for web, so time_machine is not for web in current build and Your package too...

3. flutter initialize failed Dana-Ferguson/time_machine#34
   I didn't test it, but I'm using similar version of Flutter build and it probably breaks iOS also...

Since many people works with native types, I think better solution is to use native DateTime.
I'm ready to put my effort to get rid of it, since I really like Your package and it's better to improve current one instead forking new one.