Charles Max Wood on Twitter: "If you're using Angular 1.x, I'd love to find out why you haven't moved to Angular 2.x. This is not a "You're doing it wrong" it's an exploration into a topic I'd like to cover on @angularpodcast."

Utah

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

1. Chris Tonkinson‏ @cmtonkinson 6 Dec 2017
  Replying to @cmaxw @angularpodcast
  
  In a word? Cost. Enterprise app kicked off while 1.x was live, deployed after it was already outdated. Barely enough resources to maintain, let alone nearly rebuild targeting 2.x. @dominucco has lamented about exactly this issue recently.
  
  1 retweet 6 likes
  Thanks. Twitter will use this to make your timeline better. Undo
  
  Undo
1. Shapeous‏ @Shapeous 6 Dec 2017
  Replying to @cmaxw @angularpodcast
  
  As if Angular 2 was not a complete different animal. I think many have move, they just elsewhere
  
  3 likes
  Thanks. Twitter will use this to make your timeline better. Undo
  
  Undo
1. Rob McDiarmid‏ @RobIanMcd 7 Dec 2017
  Replying to @cmaxw @angularpodcast
  
  There is a lot of overhead that comes with Angular 2+. For small projects I find I am still far more productive with AngularJS 1. Migrating to Angular 2 can be a lot of work for something that doesn't deliver any immediate value to users.
  
  1 retweet 1 like
  Thanks. Twitter will use this to make your timeline better. Undo
  
  Undo
1. Bob German‏ @Bob1German 7 Dec 2017
  Replying to @cmaxw @js_digest
  
  I need widgets, not SPAs. Angular 2 assumes it owns the whole page. Angular Elements should solve it, but meanwhile I mostly switched to React.
  
  3 likes
  Thanks. Twitter will use this to make your timeline better. Undo
  
  Undo
1. Jim Simmons‏ @rdd5280 8 Dec 2017
  Replying to @cmaxw @angularpodcast
  
  Setting the stage for possible migration to v5 - coding in 1.6, using typescript, implementing best practices. Seriously considering vue.js though at this point.
  
  1 retweet 1 like
  Thanks. Twitter will use this to make your timeline better. Undo
  
  Undo
1. Vlatoshi‏ @vlatoshi 7 Dec 2017
  This is what I'm always getting from post-angularjs devs: "I vue!"
  
  2 likes
  Thanks. Twitter will use this to make your timeline better. Undo
  
  Undo
1. thebluecheese‏ @thebleucheese 7 Dec 2017
  Replying to @cmaxw @JavaScriptDaily @angularpodcast
  
  If we had the time to do a front-end rewrite I'd be pushing for react or vue based on ease of use and likely react due to the community.
  
  2 likes
  Thanks. Twitter will use this to make your timeline better. Undo
  
  Undo
1. Alberto Santini‏ @santinialberto 7 Dec 2017
  Replying to @cmaxw @JavaScriptDaily @angularpodcast
  
  I can't, mainly because Angular doesn't support ES2015 native, without transpilation. Only recently the devs fixed the JIT part, see https://github.com/angular/angular/issues/15127 …, but removed DSL decorators https://github.com/angular/angular/commit/cac130eff9b9cb608f2308ae40c42c9cd1850c4d#diff-635fe23be5795132e3385c8f4899dc3a …. Until now the best effort is 4.x and ES5 https://github.com/albertosantini/angular2-es5-jumpstart ….
  
  2 retweets
  Thanks. Twitter will use this to make your timeline better. Undo
  
  Undo