A modern programming language that makes developers happier.

kotlinlang

New kotlinx-datetime version include formatting updates which means we can avoid some of the expect/actual stuff we have right now <https://github.com/joreilly/Confetti/pull/1159>

we still have this that we have expect/actual for....need to check again how/where this is used to see if we still need that

```interface DateService {
    fun now(): LocalDateTime
}```

I know that Clock.System.now() exists, but that gives back an Instant I think? Is that the issue with using that instead?
If yes the way that LocalDateTime is fetched right now probably makes some assumptions for the timezone. Maybe we can simply make the same assumptions while turning that Instant into a LocalDateTime so the functionality is the same but without the expect actual?

Yeah, I think there was something here about needing the time zone but haven't really looked closely at that code