Some time in the 22nd century, two leap seconds will be required every year.
The current use of only the leap second opportunities in June and December
will be insufficient, and the March and September options will have to be
used. In the 25th century, four leap seconds will be required every year, so
the current quarterly options will be insufficient. Thereafter there will need
to be the possibility of leap seconds at the end of any month. In about two
thousand years, even that will be insufficient, and there will have to be leap
seconds that are not at the end of a month. In a few tens of thousands of
years (the timing is uncertain), LOD will exceed 86,401 s, causing UTC to
require more than one leap second per day.
In 40.000 years People will hate us for three things: Global warming, Nuclear
waste, and UTC LEAP SECONDS!
Last week I got a big PDF with documentation about the almost-but-not-quite-entirely-unlike-REST HTTP API of an external partner. In the section about restrictions of their HTTP API:
For this functionality we recommend to use the SOAP API. This *convenient* interface offers almost *unlimited* possibilities to integrate Foo.
Emacs isn't just an editor, it’s an entire Emacs Lisp interpreter and
environment. We can use Emacs Lisp not only to extend and customize our beloved editor, but also to write entire programs and applications. Nic Ferrier’s elnode server is the most ambitious Emacs Lisp application of this sort, but we can start at a smaller scale and try to write our shell scripts and tools
with Emacs Lisp.
However, it turns out that writing programs in Emacs Lisp is more intricate than it looks at a first glance. Emacs decades-long history as interactive application have left deep marks in Emacs and Emacs Lisp, which make independent noninteractive scripts difficult.