3 ms·
parquet-rs: to read or write parquet files, cf the Arrow project: https://news.ycombinator.com/item?id=23966150 https://news.ycombinator.com/item?id=23966150 wh
by throwaway78123 6y ago
parquet-rs: to read or write parquet files, cf the Arrow project: https://news.ycombinator.com/item?id=23966150 https://news.ycombinator.com/item?id=23966150 where one person asking about triggered a ticket in Arrow's JIRA. I am not holding my breath (a 2.5 years old issue on Github about the exact same thing appears to be dead: https://github.com/sunchao/parquet-rs/issues/119 https://github.com/sunchao/parquet-rs/issues/119)
The web framework situation has also been a problem for quite some time. No clear stable equivalent to jetty, flask, go's net/http. Great that Diesel (which looks great) is making it to stable. I really wished it was stable 3 years ago.
On that note it would be great if crates.io would have stable/nightly compatibility as a primary concept/badge/filter. I can't think of any other mechanism to nudge library developers into supporting stable as a first class citizen.
- swsieber 6y agoI would love the stable/nightly badge on crates.io, that's a great idea. OTOH, it is nice that some libraries use nightly though because that provides some nice feedback. That said, some crates hide nightly only functionality behind a feature flag, and that'd be great to expose too. The web frameworks seem to be coming along nicely. I think the main reason for stagnation was the unstability and flux around async. Actix (stable), Warp (stable) and Rocket (stable in the next major release as all nightly features have stabilized) seem to be the strongest contenders at this point.
- steveklabnik 6y ago> (stable in the next major release as all nightly features have stabilized) I initially misread this comment; what you are saying (and what is true) is that all the features it was using are now stable, but the version that uses them hasn't been released yet. I initially thought you were saying "once all its features are stable."