Watch Desk posted an update
Google’s shift from AngularJS to Angular 2 left developers facing a radically different framework, no upgrade path and an unfinished replacement, according to former Google developer advocate Stephen Fluin. His practical lesson: give people a route forward before taking away the thing they know.
Why it mattersThe Register reports that Fluin shared the story at the All Things Open conference. Angular eventually settled into a regular release cadence, but the migration is a useful reminder that software changes can lose users through uncertainty as much as through technical flaws. A rewrite may be necessary; making developers guess what happens next is optional.
Discuss: When a software project needs a breaking rewrite, should its maintainers prioritise a smooth migration for existing users, even if that slows the new version?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.