I think I speak on behalf of most computer people when I say this: we prefer our extra hour of sunshine in the evenings not mornings.
Also, where I live there's a max of 16 hours of sunlight, and a min of 8 and a half. In the summer, it doesn't matter what the clock says, it's going to be bright when you wake up and bright when you go to sleep; so much sun. In the winter, it's most likely dark when you get up and dark when you go to bed, not enough sun that fiddling with the clocks is going to be really helpful anyway. Maybe there's a little more twilight in the morning the week after Halloween, and then it's back to morning commute in the dark. And it's pretty chilly, so while sure, I don't want to bike in the dark, I also don't want to bike in the cold, either, even if there is sun.
It's also stupid from an astronomical point of view.
It's made me realize that my being a night owl is less about the actual time and more about how I'm spending it in relation to the rest of society. There's just something about being awake when others aren't that's preferable.
Also, some states would have a real problem with permanent standard time. Maine, in particular really belongs in the Atlantic time zone, as standard time puts sunset way too early most of the year. Having the sun down by 4:00 sucks.
Which this does, because now DST is now the standard time.
For a timekeeping library (which likely uses a system-level source of data / the IANA tz database) this shouldn't have any effect.
It shouldn't be a big deal. Inevitably though, it always seems to bring the bugs out of the woodwork.