News for hackers. Stuff that matters.
Re:The Rust Platform by fnord123 on Thursday July 28, 2016 @08:20AM (#12179724)
Arrow seems particularly useless as it just wraps stdlib datetime and its awful 10 byte size rather than moving to an 8 byte representation like np.datetime64 uses.
Re:The Rust Platform by rspeer on Thursday July 28, 2016 @12:31PM (#12181282)
Just because you haven't found a use for it doesn't mean it's useless.

The stdlib datetime class is terrible and desperately needs to be wrapped. Arrow is a good wrapper. I don't know what you're on about with counting bytes.

Re:The Rust Platform by fnord123 on Thursday July 28, 2016 @05:32PM (#12183342)
I've wrapped datetime for company work (pre pandas, pre datetime64) to make sure it follows the rules of the data analysis platform we developed (adding functions for moving to next month of year based on various financial calendar rules for example). I wish I hadn't done it and had just wrapped a boost_datetime since the performance of datetime is slow when you have a large timeseries of them. The performance is especially unacceptable if you also have timezones attached to your datetimes.

Now we have pandas, yay. But I don't see why one would use arrow. If you're patient enough, could you explain why you would use it? The website doesn't seem to be very convincing.

Re:The Rust Platform by rspeer on Friday July 29, 2016 @03:43PM (#12189413)
Not everything is a DataFrame. You would use Arrow because you want a nice API for dates and times in use cases that have nothing to do with Pandas.