Platform Wars
summary
A concise market model links concrete tools to the platforms that enable or strangle them: examples include Rider vs Visual Studio where JetBrains builds a cross‑platform IDE (Rider) by porting ReSharper and replacing a removed debugger after a license dispute, Unity choosing Visual Studio by default but integrating Rider features, Microsoft buying Xamarin to prop .NET into the cloud, and Kotlin evolving into a platform after Google names it preferred for Android; outcome: tool–platform dependencies often decide which technically superior products survive.
AI-written summary · about
chapters (14)
- 0:00Introduction to Platform Wars
- 1:10Business aspects of tech
- 3:21Failed tech examples
- 8:03JetBrains market experience
- 15:39Tool-platform dependency model
- 21:18Visual Studio vs Rider example
- 27:02Cloud solutions competition
- 35:41Windows Phone and Silverlight analysis
- 38:50Kotlin as JetBrains platform
- 42:00JetBrains product successes and failures
- 47:23Competition with Microsoft and Google
- 50:35Q&A 1
- 55:15Q&A 2
- 1:00:35Q&A 3
related talks
34mPlatforms: Defying the laws of IT physics
58mPlatforms: Build abstractions, not illusions
43mPanel: The Platform Rock-Paper-Scissors: Build, Adopt, Buy
51mThe Magic of Platforms
24mSignificance of Platforms in Product Development
54mThe Development Platform Landscape in 2018
26mThe Past, the Present, and the Future of Platform Engineering
26mNative Vs Hybrid Vs Cross‑Platform: Dreams and Realities