It's like, does it really matter that much? Can't we want until it's saved up more?
---
"You can't keep throwing people at your problems, dear." - Emma Frost to Colossus
~Jacehan~
As someone who has endured the pain of implementing leap-second handling for a programming language (Perl 6), I can say that no, you're not the only one. But I'm not sure a leap minute or leap hour would be easier to deal with, since although if it would be rarer, it would be much more dangerous to ignore. One idea that I haven't heard anybody mention is to use a unit of time that's so small that it would be within the margin of error of most timekeeping devices, such as the nanosecond. That wouldn't make date arithmetic any easier, but at least it would remove the "bumps" in timekeeping created by leap seconds.
---
"did you know that in real life all those stats for how often the average person thinks about sex are ACTUALLY about ice cream?"
Yeah it's weird! I feel like maybe 15-minutes is the smallest amount of time that we need to worry about in terms of correcting. Like, it might throw people off biologically if we're expected to still wake at 7-ish in the morning and sleep at 11-ish at night and it got an hour or two out of sync. But we can save up 15 minutes!
Honestly, we wouldn't have this huge mess if we could change the orbital rotation of Earth by that tiny fraction of a second.
---
"I always wanted to be somebody, but now I realize I should have been more specific."
We couldn't just do that once; we'd have to do it over and over again. The problem is that the speed varies unpredictably, not that it happens to not be a whole number of seconds.
---
"did you know that in real life all those stats for how often the average person thinks about sex are ACTUALLY about ice cream?"
Indeed, if the problem were the latter, the sensible thing to do would be to change the duration of the second.
Both methods have to be done over and over, but my method involves more explosives, so we should go with that.
---
"I always wanted to be somebody, but now I realize I should have been more specific."