PermaCal
PermaCal
[Megan and Cueball are in the panel. Cueball appears to be holding a phone, tapping.] Megan: What day is it? Cueball: Sunday the 19 th . Megan: But you said it was the 19 th yesterday. Cueball: It changed again ?  Crap, better add another leap day. [Caption below the panel:] My simplified calendar system assumes the date never changes, then corrects any drift via leap days.

This comic proposes a new calendar system, named PermaCal (a malamanteau of the words "permanent" and "calendar"). In it, the date stays constant. In order to accomplish that, as each day passes, it is interpreted as "drift", and a new PermaCal leap day (analogous to the leap day of the Gregorian calendar ) is added to compensate.
In the comic, which was published on Monday April 20, 2015, Megan wonders why today would be the 19th, since Cueball said it was the 19th a day ago. Cueball interprets the news from Megan, that a day has passed, as "drift" in the date, and resolves to add another leap day to PermaCal so that his calendar will be correct. He is presumably becoming frustrated that he has to do this so often.
Leap days in the Gregorian calendar are days added to the end of February every year that is a multiple of 4, but not by 100, unless it's also a multiple of 400. The purpose is to synchronize the calendar with Earth's orbit without having a partial day each year. Leap seconds are necessary because the earth rotation is not constant, but speeds up and slows down over time. The leap seconds account for the differences in the length of our 24 hour day and a solar day (the time taken for Earth to rotate once with respect to the sun), and are announced several months beforehand.
NTP servers are used to keep local computer time from drifting. They also are used to announce Leap seconds . In the context of this comic, leap seconds would refer to a different system in which there is a new leap second each second, so the time also stays constant, down to the resolution of one second. This would require something like setting the NTP leap second bit anew every second. The title text presumably refers to moving to a resolution of one millisecond via leap milliseconds. This would require at least 1000 updates being requested every second, using enormous network bandwidth and resulting in a Distributed Denial-of-service attack (DDoS) situation.
The comic relates to several DDoS problems due to NTP server misuse and abuse over the years.
Part of the humor stems from the problems that leap seconds are causing for some computers. [1] The last leap second disrupted computers at big companies such as Reddit , LinkedIn , Gizmodo and FourSquare . Google first introduced a new approach of smearing the leap second , smoothly changing the reported time over an undisclosed number of hours around midnight UTC on December 31, 2008. The smooth shape of the adjustment is graphed at synchronization - Math behind Google leap second smear formula - Stack Overflow .
A new calendar was also proposed in comic 1061: EST .
[Megan and Cueball are in the panel. Cueball appears to be holding a phone, tapping.] Megan: What day is it? Cueball: Sunday the 19 th . Megan: But you said it was the 19 th yesterday. Cueball: It changed again ?  Crap, better add another leap day. [Caption below the panel:] My simplified calendar system assumes the date never changes, then corrects any drift via leap days.
