Big tech is here to let us down
A major Microsoft cloud and Outlook outage has renewed anxiety over how much modern businesses and governments depend on a handful of big tech platforms for email, office software, and core infrastructure. Commenters argue that centralizing everything on Microsoft, Amazon, or Google creates systemic risk, soft targets for cyberwarfare, and brittle monocultures, yet note that deep integration, feature richness (especially Excel), compliance requirements, and vendor lock‑in make large-scale migration extremely costly. Proposals range from stricter regulation and mandated redundancy to greater use of open source, on‑premise systems, and AI-assisted custom tools, but many doubt that market or political incentives are strong enough to drive meaningful change.
Scope of Blame for Outages
- Some argue Microsoft and other hyperscalers should compensate for business losses; others note even huge state-caused damage (e.g., hoarded exploits) never led to compensation.
- Several comments shift blame from “big tech” to executives who chose single-vendor, cloud-centric stacks for cost and convenience.
- SLAs are seen as weak protection; real-world downtime and dependency risks are higher than buyers admit.
Centralization, Cloud, and Systemic Risk
- Heavy reliance on a few clouds is framed as a massive single point of failure, including as a soft physical target in war.
- Concentrating many banks or critical systems on one provider leads to correlated failures.
- Some argue many organizations could self-host again or diversify, but switching back is politically, economically, and technically hard.
Dependence on Microsoft and Excel
- Outlook/Office/Exchange are described as deeply embedded in business processes and file formats, making migration extremely costly.
- Excel is portrayed as irreplaceable for many: database, calculator, visualization, collaboration, and “back-of-the-napkin” tool in one.
- Others counter that most users use only basic features, so lighter or open alternatives might suffice for a majority.
Alternatives and AI-Driven Replacements
- Suggestions range from LibreOffice, Google Workspace, custom tools, and niche sheets to open-source OS/Excel “killers.”
- Many are skeptical that AI-vibecoded clones can match decades of features, integrations, and edge-case behaviors, or be maintained long term.
- Some foresee AI helping users build bespoke, local tools; others see this just replacing one form of vendor lock-in with another (e.g., “OpenAnthroogle rent”).
AI, Code Quality, and “Vibecoding”
- Debate over whether AI-written code is contributing to outages: some see widespread low-quality “slop,” others say outages and bad ops long predate LLMs.
- Concern that management treats “coding as solved,” while reliability and operations remain hard, under-resourced problems.
Regulation, Markets, and Resilience
- Disagreement over whether the problem is “central planners” or unregulated markets and oligopolies.
- Some call for regulation forcing critical infrastructure and banks to avoid over-centralization; others advocate letting markets correct.
- A minority argues most industries should tolerate occasional “snow day” downtime; critics respond that tolerance reduces pressure to fix structural risks.