You're not a software developer, are you ;)? I'm not working on any timezone-aware products right now but I feel for all my brothers and sisters in the trenches if this passes and has to be fixed everywhere!
Things have improved though: back in the 2000s when the 'Bush DST' change occurred, all sorts of software had hard-coded assumptions.
This is because US developers, who wrote a good portion of OS and other software, had never experienced a tzdata update first hand. So that when (e.g.) PST8PDT had its rules changed, it turns a lot of stuff needed to be rebooted to pickup things up.
A bunch of code was put in to notice changes dynamically, so in 2026 things should hopefully be smoother if there are new rules.
Having experienced both I would take the no time change every time. And I have yet to meet anyone who would (small sample size for sure, I'm sure someones done some polling).
https://www.ktvb.com/article/news/local/idaho/locking-the-cl...
Our representative Mike Simpson voted for it. He has done some good things compared with our other congressional delegates (Mike Crapo, Jim Risch and Russ Fulcher) who tend to make fly by night committee votes against whatever is popular with the general public, so I don't want to knock him. But he does represent district 2, which is 200 miles to the east and would have a sunrise closer to 9:00 am:
https://ballotpedia.org/Idaho%27s_2nd_Congressional_District
My feeling is that permanent DST is just not gonna fly here. So if it passes, our elected officials will take a lot of flack for it and have to run damage control.