4 ms·
I agree with functional first for backend programs. I don't see functional programming become popular on the front-end thought.
by cmoscoso 10y ago
I agree with functional first for backend programs. I don't see functional programming become popular on the front-end thought.
- christophilus 10y agoI disagree. It is the frontend that made me want to learn functional programming in earnest. Redux and ImmutableJs were the catalysts. I'm currently learning a couple of LISP variants (Closure and LFE). With ClojureScript, Elm, PureScript, BuckleScript, and even plain ole ES6, functional on the frontend is more compelling than ever.
- lucasmreis 10y agoI disagree too. Frontend is getting more complex each day, and I find that functional programming languages help a lot with large projects. Frontend SPA's are crying for help with the exploding complexity :)
- cmoscoso 10y agoGood point on the complexity of today web apps. I'm not really into web front-end and my comment was more about native frontend development, where you need to add/remove things from screen, run animations, you know, those sort of things that are inherently non-functional. Sorry for not being clearer.
- lucasmreis 10y agoIt's ok! :) So, if we only want to call a couple of animations and submit a form, I agree that a small script with three jQuery-style functions can do the job. But that's rarely the case nowadays, in my experience. Almost every frontend project I came across professionally became a full application at some point. There's the need of dealing with concurrent user interactions, online data requests to the server, non-traditional form behaviors, different routes...
- banashark 10y agoHere is an example of something small that can benefit from F# sharing: http://banashek.com/posts/20170204-a-brief-peek-at-universal-fsharp.html http://banashek.com/posts/20170204-a-brief-peek-at-universal... Sharing types, validators, etc mean that the api communication is type-safe.
- lucasmreis 10y agoReally good, amazing example