4 ms·

Yeah, but if you are opposed to functional programming (or opposed to exposure to any new programming paradigms) of course you’ll hate the library that has had

Yeah, but if you are opposed to functional programming (or opposed to exposure to any new programming paradigms) of course you’ll hate the library that has had perhaps the largest impact in bringing concepts from functional programming into the mainstream. That’s perfectly understandable. But I like functional programming and I very much like React’s impact in this area.

dexwiz 5y ago
Using Functional Paradigms in a FP language. Cool! All for that. Bootstrapping pseudo FP styles into a Prototype Language with no types (JS is technically not OO, even `class` is just prototype sugar). Please no. I really like concepts behind FP. I have tinkered with Haskell and gone through Bartosz Milewski's Category Theory material. That said, its radically different than traditional Procedural or OO coding. It really needs language level support to be useful, and that usually starts with types and the compiler. Open up "FP" libraries in non FP languages, and you often discover its just the same objects as the rest of the language. That said, immutability is awesome. The concept of creating mutability boundaries and only exposing immutable data to external services and clients solves a whole class of bugs related to "who changed that?"