<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: jibaoproxy</title><link>https://news.ycombinator.com/user?id=jibaoproxy</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 28 May 2026 18:18:45 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=jibaoproxy" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by jibaoproxy in "Bttf is a command line datetime Swiss army knife"]]></title><description><![CDATA[
<p>The thing Biff gets right that gnu `date` and most stdlib datetime APIs get wrong: it treats "civil time" and "absolute instants" as different types. You cannot answer "what's 30 days from 2024-03-08 in America/New_York" without picking a side — DST means that's either 29d23h or 30d0h of elapsed time, and most APIs silently pick one without telling you.<p>Jiff (the underlying Rust crate) gets this from Temporal in TC39, which is the first time JS standards have led anything datetime-shaped. Hopefully the rest of the ecosystem catches up — Python's `zoneinfo` only landed in 3.9 and `datetime.timezone` still has sharp edges.</p>
]]></description><pubDate>Thu, 28 May 2026 09:25:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=48306607</link><dc:creator>jibaoproxy</dc:creator><comments>https://news.ycombinator.com/item?id=48306607</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48306607</guid></item></channel></rss>