Ok, why do people keep doing this:

library(tidyverse)
library(lubridate)

when the first call automatically loads the package in the second call? Am I missing something here?

I see this **everywhere**!

#rlang #rlanguage #tidyverse #lubridate

Day 22 | Timeseries – Stars | #30DayChartChallenge. Visualization made with R using #ggplot2, #dplyr, #showtext, #lubridate and #cranlogs. | Source: cranlogs R Package.
Día 11 | Distribuciones – “Stripes” | #30DayChartChallenge. La visualización fue creada usando R basado en los paquetes: #ggplot2, #dplyr, #sf, #lubridate, #ggtext, #showtext, #RcolorBrewer, #rnaturalearth y #cowplot. Fuente: CHIRPS.
@danwwilson @lwpembleton #brms by @paul_buerkner has made Bayesian models incredibly fun and intuitive for me. I love the combination of well thought out defaults and API with a lot of depth and power, should you need it. Other than that, I think #lubridate needs some love! Oh and #igraph, which just works ™️ plus it's lovely descendant #tidygraph 🕸️
#packagelove

Thanks to #lubridate parsing at work in {ggcalendar}, you can switch to Monday week start if you so choose with options call.

options(lubridate.week.start = 1) # change to Monday start, 7 (Sunday) is lubridate's default

Thanks @minga for inquiry! Example w/ flights data - number of flights drop on the weekend. Sat and Sunday positioned at the end of the week because of the options call! #ggplot2

Meeting planning w/#ggplot2, #lubridate, #hms, is looking like this. Not expecting much participation for Adelaide for this one... 🙃
@antimnguyen The #tidyverse people strive to invent catchy names for their packages, I like #lubridate best, which simplifies arithmetics with date and time.