<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lubridate on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/lubridate/</link>
    <description>Recent content in Lubridate on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 27 Nov 2021 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/lubridate/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>{itdepends} on {lubridate}</title>
      <link>https://www.rostrum.blog/2021/11/27/lubridate-fns/</link>
      <pubDate>Sat, 27 Nov 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2021/11/27/lubridate-fns/</guid>
      <description>tl;dr I used {itdepends} to see how CRAN packages depend on {lubridate}, which was not removed from CRAN recently.
 Lubrigate A test failure in {lubridate} led to hundreds of R developers being emailed about its potential expulsion from CRAN, which also threatened the hundreds of packages that depend on it.
I see the benefit of minimising dependencies. I also understand the drawbacks of reinventing the wheel. Maybe {lubridate} is a good dependency: a simple API, part of the popular {tidyverse}, and it handles stuff you can’t be bothered with (like what’s 29 February plus one year?</description>
    </item>
    
  </channel>
</rss>