Oh yeah, no argument there. While we have the technology to implement something like this pretty quickly, the legislature does not move as fast.

Yep, and my rebuttal was that if it passed now (or even in the next few months) i believe orgs would have plenty of time to implement the change before the next clock change in the fall.

Yep, I'm one of those people who works in said environments. I can say, with confidence, that with automation available at the orgs you mention (Commonly MECM, Intune, or GPO for Windows and Ansible for Linux/anything else SSH) this change would be pretty dang trivial.

Windows Registry example (likely delivered through GPO, MECM, or Intune) - This would cover most use-cases for the environments you mention.

To add, I also work in one of those "regulated industries" (government/defense). There are specific processes for stuff like this that requires quick action and to bypass normal CCBs. An example for the gov/mil side is when 0-days are discovered (think SolarWinds and Log4J). Do they want to spend months testing and approving? Hell no! While flipping a time-zone config isn't exactly the same as remediating a vulnerability, fixing it would be important to business continuity to justify some expedited changes.

> The actual change might only take a couple days to roll out, but it's not like companies have people sitting around waiting to do this, they have day to day business to take care of as well.

Most of the companies you mentioned in regulated industries do have folks that spend their work day doing this. People like ISSOs/ISSMs, change/config managers, automation engineers just to name a few. It is their business to stay abreast of upcoming changes and respond.

Not really. Most internet enabled devices would probably get it on their regular round of updates. Just a switch to no longer flip between $ST and $DT. Most apps go by system time anyway so they’ll go by whatever device time is. The only thing that would be a pain would be anything that doesn’t receive automatic updates or anything not internet-connected.

IANAL, but this is my understanding. Too many people think there's some law that prevents employers from saying anything negative about an employee (justified or not). The only recourse someone has is a civil suit where they have to prove some sort of slander (hard to do, as I understand).

> It costs time and money to argue over what’s true and what’s defamatory

Those same costs apply to both sides. The person who is accusing the business of slander will need to be able to eat those costs. I would say in most cases businesses are in a better position to argue those cases than an individual.

Unless one gets some sort of proof that's hard to prove.

>2A open carry BS

Just to clarify; do you mean open carry (IE carrying in a non-concealed, conspicuous holster) or constitutional carry (IE carry of firearms without permits)? Because it's totally legal, although likely frowned-upon, for a FID holder to open carry their firearm.

Even if this came true, people would still consider “western Mass” as anything west of Worcester.