You can do checkbox exercises all day, won't make a difference.
Nearly all banks have long long lists of certification, they still have extremely bad customer-side security processes because you can "interpret" various guidanecs and pay the right auditors enough to have it ignored.
Again, Microsoft doesn't control modules people choose to use and can't assume anything about how they work, much less disable them without operator approval.
Imagine if malware could somehow crash this module - would you be happy about the OS automatically rolling bank introduction of said module, opening your system to vulnerabilities?
I think the point GP was making was that you restrict yourself to only the bundled standard library, which covers most of the basics needed for scripting.
This is why you force yourself to use nearly zero dependencies. The standard library sys, os, subprocess, and argparse modules should be all you need to do all the fancy stuff you might try with bash, and have extremely high compatibility with any python3.x install.
Or they don't want to spend half their time managing that Jenkins ecosystem when some bash scripts and literally any other CI solution out there gives you very similar benefits for fraction of the effort.
OneDrive fucking sucks. If they didn't advertise it constantly through Windows I don't think anyone would know it exists. Google Drive gets used sometimes, but only slightly more frequently than Dropbox.
In SOC2 compliant orgs it's really not very common to store your files with BigCorp. At least, it's one of the no-nos they try to impress on you pretty early.
This would require open source projects to allow something like that, I can easily see an influx of low quality PRs with vetting burden put on the OSS community rather than the HR tech startup or the recruitment company.
Yes, from startup and Company employer angle it looks perfect.
Communities - yes, the burden will rise, but they will benefit anyway: more commits, more developers involved, more new ideas, more popularity, etc.
