Marc Knaup
05/21/2019, 2:35 PMjava.time
API and Swift's date/time API, multiplatform starting with JVM & iOS.
At first it'll make use the underlying platform APIs (using threeten backport for Java, native for iOS) while building a good common API.
Over time more and more of the underlying API can be replaced with own common code.
Be aware that everything involving time zones, date/time calculations and date/time parsing is a shitload of work 😄josephivie
05/23/2019, 5:28 PMlokalize
and there's already a klock
that most people use. +1 for going with good naming conventions on your types. I might suggest using inline class
to make the whole thing more efficient. You have my explicit permission (though the license already covers it) to pull whatever you might want from lokalize
for fluid-time
. You're also welcome to contribute to mine too if you'd like.Marc Knaup
05/23/2019, 5:39 PMjosephivie
05/23/2019, 5:57 PMjava.time
. I'm very much not, so I just used an inline class for my time stamp, using milliseconds since 1970 - I just haven't needed that level of precision on time stamps yet, and I built mine strictly for being able to make my multiplatform UI library.napperley
05/24/2019, 11:11 PMnapperley
05/24/2019, 11:14 PMMarc Knaup
05/25/2019, 11:15 AMLong
so it should be fine 🤔