3 ms·

Could you elaborate on your statement that intellisense is associated with bad code? Intellisense is available for just about every language under the sun, so c

by garren 5y ago

Could you elaborate on your statement that intellisense is associated with bad code? Intellisense is available for just about every language under the sun, so clearly this isn’t a TS specific issue. Even dynamically typed FP langs have pretty solid language servers these days. You also seem to suggest that FP and types are somehow opposites. What are your thoughts on a strongly typed functional language like Haskell, Idris, or an ML-derivative? Regarding your thoughts that TS makes FP more difficult, more than, say, C++ or Java? I’ve found that one can write FP style code in just about any language, though some obviously make it easier than others. I don’t use TS, but I would have thought that its JS roots and then fact that it’s fairly flexible regarding how strictly one can adhere to its type system, would lend itself to an FP style well.

tacotacotaco 5y ago
Again, I have nothing against type systems. As you pointed out some languages make FP easier than others. C++ and Java's type system, from which TS's type system descends, are not FP languages. You _can_ write functionally but they do not afford much ease. Intellisense does make code easier to write, good code and bad code. Yes, in all languages. My concern is that every colleague I have spoken with about TS conflates this ease of writing code with better code. It's not. They are still writing highly coupled, imperative code but now with types. Garren pointed out in another comment the book "Domain Modeling Made Functional" which I have read and have recommended to several other devs. It provides a great example of using type system effectively. While TS's type system isn't quite the same as F# I think a good portion of this book still applies, both types and composition. JS will be getting a pipeline operator and pattern matching in the near future. I expect TS will be updated to support them. This makes FP more relevant.

by garren 5y ago

tacotacotaco 5y ago

Again, I have nothing against type systems. As you pointed out some languages make FP easier than others. C++ and Java's type system, from which TS's type system descends, are not FP languages. You _can_ write functionally but they do not afford much ease. Intellisense does make code easier to write, good code and bad code. Yes, in all languages. My concern is that every colleague I have spoken with about TS conflates this ease of writing code with better code. It's not. They are still writing highly coupled, imperative code but now with types. Garren pointed out in another comment the book "Domain Modeling Made Functional" which I have read and have recommended to several other devs. It provides a great example of using type system effectively. While TS's type system isn't quite the same as F# I think a good portion of this book still applies, both types and composition. JS will be getting a pipeline operator and pattern matching in the near future. I expect TS will be updated to support them. This makes FP more relevant.