Microsoft is killing Skype

Original Article ↗ Hacker News Discussion ↗

Immediate reactions & legacy

  • Many say Skype “died years ago”; this is seen as the formal obituary rather than a real-time death.
  • Strong nostalgia: memories of early 2000s cheap international calls, long-distance relationships, studying/working abroad, Nokia days, and the iconic ringtone.
  • The “to skype” verb for video-calling is still common in some languages; several note the irony that the brand remained strong even as the product degraded.

Perceived mismanagement and strategy

  • Widespread view that Microsoft bought Skype mainly to neutralize a competitor and funnel users into Lync/Skype for Business and ultimately Teams.
  • People recount confusion and fragmentation: MSN/Live Messenger → Lync/Office Communicator → Skype for Business (really Lync) → Teams; multiple incompatible “skypes” on the same machine with arbitrary calling restrictions.
  • Users complain about forced Microsoft account linkage, phone-number requirements, aggressive upsell, UI churn, and “enshittification”.

Architecture changes & technical issues

  • Several recall original Skype as a technically impressive P2P system with “supernodes” that worked over terrible connections and even local-only LANs.
  • Microsoft later centralized the architecture, which users associate with worse performance, higher resource use, sync issues, and easier surveillance.
  • Developers and reverse‑engineers say large parts of the modern Teams stack (protocols, calling infrastructure) derive from post‑P2P Skype, layered with more complexity; Skype’s codebase is widely described as an unmaintainable mess.

Covid, Teams, and enterprise vs consumer

  • One camp argues Microsoft “dropped the ball” by not using Skype to dominate pandemic video chat, letting Zoom and others take the mindshare.
  • Another camp counters that Microsoft “nailed it” on the enterprise side: Teams, deeply bundled with Office 365, exploded to hundreds of millions of users and huge revenue.
  • Consensus: Microsoft is now focused on B2B; consumer communications (Skype, “Teams for consumers”) are underinvested, confusingly branded, and often disliked.

Use cases being lost & migration pain

  • A major concern is loss of cheap VoIP to landlines, toll‑free, and international numbers, plus Skype Numbers used as stable US lines from abroad.
  • Others worry about elderly and non‑technical relatives who only ever learned Skype and will now need to be re-onboarded to something else.

Alternatives being discussed

  • For VoIP/PSTN: SIP/VoIP providers (voip.ms, Callcentric, Anveo, Ippi, MobileVOIP, Viber, Vyke, TextNow, Google Voice, jmp.chat, Google Fi, Tello, Zadarma) with caveats around SMS, caller ID, cost, and “scammy” UX.
  • For consumer chat/video: WhatsApp, Signal, Telegram, Discord, Jitsi Meet, Google Meet/Duo, FaceTime, Matrix, Jami, Tox; each has trade-offs in privacy, platform support, and ease for non‑technical users.

Data, credits, and lock‑in

  • Users report expired or silently “gulped” Skype credit; others paste Microsoft’s email promising credits will still be usable via Teams/web but no new subscriptions.
  • People are exporting chat history and discovering that pre‑cloud, P2P-era logs only exist in local client databases.

Broader reflections

  • Thread repeatedly compares this to Nokia: another European success story bought and “strangled” by a US giant.
  • Many see this as yet another case of big-tech acquisition → brand hollowing → bundling competitor into a larger suite (Teams) → eventual shutdown.