Having used both, NACS is more compact, so both the port on the car and the end of the cable are significantly smaller than CCS. The cable itself is also lighter and more "usable" than CCS. At least at the newest V3 superchargers, the NACS cable is so much more flexible and easier to manage.
For 3, enable Reduce Motion under System Settings > Accessibility > Display.
This makes switching spaces and windows nearly instant with no animation. I don't notice whatever else lost animations...so I don't miss them. Worth a try!
Definitely worth keeping in mind the business needs. I'm not going after "well designed security that meets the business needs". I'm calling out lazy security that cuts corners because doing it well takes time and effort.
That being said, there is also a real, significant business cost to leaking sensitive information. If users are frequently waiting for access or unable to discover data, that's a failure in understanding the users needs and/or failing to test those needs in UAT during implementation. Convenience should never trump security, in this context.
> “My team is frustrated by the permissive nature of the platform,” Carbee said.
As someone who implements Salesforce projects for companies like this, I place the blame solely on whoever setup that Vermont org. Salesforce's permissions are very, very powerful and flexible, which also makes them complex. Salesforce recommends and works best with a "least privilege" security model.
It is frustrating to me how often I see colleagues (and some clients) push for a "wide open" permissions structure, where every internal user can see everything unless otherwise specified. It's just laziness towards doing it the right way. During a brand-new Salesforce implementation for a multi-thousand user company, the stakeholders pushed me hard for an open policy. "We trust our employees". Ugh.
Munro Live took both connectors apart and did an overview: https://www.youtube.com/watch?v=gmjofPpThWU