Yarn's Future – v2 and beyond

Re:Yarn's Future – v2 and beyond by LaGrange on Thursday January 24, 2019 @10:53AM (#18989704)

Facebook (excuse me, bunch of FB employees from the Flow team) says no: https://github.com/facebook/flow/issues/7365#issuecomment-45.... Of course, that's exactly what I'd say if I was in charge of a dying project.

Edit: but, their main codebase is in Flow, and that sounds like a mess to migrate, so I wouldn't be _too_ worried. It might slow down, but I doubt it will become unmaintained anytime before Facebook gets sued out of business :-P

[ Parent | on HN ]

Re:Yarn's Future – v2 and beyond by kimsk112 on Thursday January 24, 2019 @11:19AM (#18990008)

I recalled when Microsoft employees and MVPs denied when Silverlight was dying. :-( I think the TypeScript momentum is too strong now.

[ Parent | on HN ]

Re:Yarn's Future – v2 and beyond by LaGrange on Thursday January 24, 2019 @04:47PM (#18993336)

I think Flow's in more direct trouble, but I wouldn't announce victory for TypeScript just yet. With wasm around the corner, things may (or may not, shrug) change significantly.

[ Parent | on HN ]

Re:Yarn's Future – v2 and beyond by int_19h on Thursday January 24, 2019 @08:29PM (#18994740)

Even with wasm, much as I'm looking forward to the Great JS Purge personally, it's not going to happen anytime soon - too much existing code and devices. JS will remain necessary on the front-end for at least another decade, and probably beyond that. So TS will still be necessary to make the pill less bitter.

[ Parent | on HN ]