Yarn's Future – v2 and beyond

Re:Yarn's Future – v2 and beyond by cphoover on Thursday January 24, 2019 @04:06PM (#18992969)

I'm a fan of functional programming over OOP as such, I don't need all of the OOP constructs just give me some immutable primitives, first-class functions and let's get to work.

There's not much I can do with a class that can't be accomplished with a simple function.

I think I've evolved in my thinking over this in the last several years of experience.

[ Parent | on HN ]

Re:Yarn's Future – v2 and beyond by fold_left on Thursday January 24, 2019 @04:56PM (#18993432)

You can continue to code the way you've been enjoying, just with the option to type your inputs and outputs if you choose to. Writing classical OOP isn't imposed on you by TypeScript, nor do you miss out on anything by not writing classical OOP.

[ Parent | on HN ]

Re:Yarn's Future – v2 and beyond by Siilwyn on Thursday January 24, 2019 @05:04PM (#18993499)

Typescript doesn't support typings for functional concepts that libraries like Ramda & Sanctuary use though.

[ Parent | on HN ]

Re:Yarn's Future – v2 and beyond by fold_left on Thursday January 24, 2019 @05:37PM (#18993759)

That's also true. TS has more to do to improve working with functional JS.

[ Parent | on HN ]