[AReallyGoodName]

Well having one aspect related to sun position (leap seconds) living in the raw seconds counter and all other aspects related to sun position (time offset, leap years, etc.) living in the human readable date formatting functions is unacceptable imho.

We either get rid of leap seconds in UTC time and treat leap seconds as a date formatting issue or we somehow get all OSes, libraries and applications to start using TAI time as their fundamental time counter instead (this is preferred but it's a lot of work, so yeah you're right about it being laziness).

Or i guess we can just continue living with the inconsistency of some sun position stuff being in the time counter and the rest in the date formatting functions (ick! there's a reason this is causing bugs all the time!).

[ambrop7]

I say it's preferable to eliminate leap seconds from UTC time and treat them as part of the calendar. It's not lazyness, it's just sane design. If everything was measured in calendar time, there is a lot of inefficiency involved for anything which does not need calendar time like calculating intervals.