I haven't spent much time thinking about what a package in Roc for dealing with time would look (aside from the obvious elm/time) but this comment is an interesting example of things a Roc time design should consider that elm/time doesn't need to in the browser
That's an interesting problem that I would bet many people never think about.
elm/timedoesn't need to in the browser
fun fact: "more than one clock" is true in the browser too: new Date() and performance.now() will drift apart from one another, even.
Last updated: Jun 16 2026 at 16:19 UTC