Cool! Great and awesome feedback. The summary is that Joda-Time is what we should aspire to have.
My goal is to first cover the "most common use cases", and as Corey says, "easy to use correctly". After that I can start considering the corner cases like bya and mya. Which sound very fun and interesting, but not high priority. Hopefully by then I won't be too consumed by the question of what is Time. Thanks, will keep you guys updated, Luis On 13 September 2013 16:20, Thad Guidry <[email protected]> wrote: > Additionally, > > Be able to convert "bya" to "mya" ? http://en.wikipedia.org/wiki/Bya > > The short scale is now commonly used, btw... but also need to deal with > this for conversions: > > http://en.wikipedia.org/wiki/Long_and_short_scales > > There should be a preference boolean for conversion output for short or > long scale... especially concerning above a thousand million. > > That's enough to get you going with some wild ideas that Jodatime does not > handle. > > > > On Fri, Sep 13, 2013 at 3:08 PM, Thad Guidry <[email protected]> wrote: > >> One idea and use case for Paleontologists and Geologists coming over to >> Rust in droves... :-) >> >> Generically, just be able to handle simple Geologic addition and >> subtraction against an Epoch itself (reference date) >> http://en.wikipedia.org/wiki/Epoch_(reference_date) using known >> abbreviations. >> >> And additionally, store, understand, and output them: >> >> B.Y.B.P = Billion Years Before Present >> M.Y.B.P = Million Years Before Present >> >> >> >> >> On Fri, Sep 13, 2013 at 2:51 PM, Aaron Dandy <[email protected]>wrote: >> >>> I remember reading this article: >>> http://noda-time.blogspot.com/2011/08/what-wrong-with-datetime-anyway.html a >>> while back and really appreciating date time & time zone libraries. Also >>> after reading news of the leap second triggering a bug on a bunch of >>> systems I now question all assumptions I make about our representations of >>> time. I can no longer say that a minute is 60 seconds long with a straight >>> face. Next up I guess we programmers have a year 2038 problem to deal with >>> too. This library will be a big deal to write but there thankfully there >>> should be a lot of existing knowledge to learn from. >>> >>> ------------------------------ >>> Date: Fri, 13 Sep 2013 15:10:21 -0400 >>> From: [email protected] >>> To: [email protected] >>> CC: [email protected] >>> Subject: Re: [rust-dev] lib: Is anybody working on the datetime library? >>> >>> >>> Hello Bardur, >>> >>> Thank you so much for the reference resource of JSR-310 and its design >>> docs. >>> I looked over it briefly and it is indeed very valuable. >>> >>> It was listed in the wiki page, but the link was to the former home of >>> it. >>> I have updated it. >>> >>> Since nobody has claimed this module, I will start working on this >>> module tomorrow Saturday. >>> Is that OK? >>> >>> Please, please, I would love more comments and ideas. Will start asking >>> for reviews once I have some code to show. >>> >>> Thanks, >>> Luis >>> >>> >>> >>> >>> >>> On 13 September 2013 00:57, Bardur Arantsson <[email protected]>wrote: >>> >>> On 2013-09-12 22:12, Luis de Bethencourt wrote: >>> > Hello everyone, >>> > >>> > I'm interested in helping with some module development. A good way to >>> learn >>> > Rust by using it and help Rust at the same time. >>> > >>> > Of the wanted modules in this page: >>> > https://github.com/mozilla/rust/wiki/Libs >>> > >>> >>> I see that this page does have a link to design docs for JSR-310 which >>> is probably a good bet as to a usable DateTime API design (for Java at >>> least). I just thought I'd mention that the documentation for the >>> "nearly final" (i.e. barring serious bugs) API has been released at: >>> >>> >>> http://download.java.net/jdk8/docs/technotes/guides/datetime/index.html >>> >>> Even if this is for Java, the design decisions about how the conepts of >>> date/time are modeled (Instant vs. *DateTime, Periods, Durations, etc.) >>> would apply in any language. They are also all essential concepts when >>> working seriously with date/time even though the distinctions may not >>> appear so at first. >>> >>> (I should mention that the lead on the JSR-310 spec was also the author >>> of JodaTime which gets much deserved credit by Java developers for >>> bringing date/time manipulation on the JVM out of the dark ages of >>> java.util.Date. JSR-310 is a slightly reworked/simplified version of >>> that API, so it's a sort of "what are the essentials?" version of >>> JodaTime.) >>> >>> Regards, >>> >>> >>> _______________________________________________ >>> Rust-dev mailing list >>> [email protected] >>> https://mail.mozilla.org/listinfo/rust-dev >>> >>> >>> >>> _______________________________________________ Rust-dev mailing list >>> [email protected] https://mail.mozilla.org/listinfo/rust-dev >>> >>> _______________________________________________ >>> Rust-dev mailing list >>> [email protected] >>> https://mail.mozilla.org/listinfo/rust-dev >>> >>> >> >> >> -- >> -Thad >> Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry> >> Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/> >> > > > > -- > -Thad > Thad on Freebase.com <http://www.freebase.com/view/en/thad_guidry> > Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/> >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
