I tried Ramda and I don't see the benefit of writing code differently, words like thousands of people are doing it doesn't mean everyone else should do it.
I am not saying it is bad, and again scientific applications was an example, not an absolute statement, you have to evaluate what is best in terms of maintainability, availability of talent and tooling, and whether application really requires functional stuff or not.
This is the biggest problem with developers today, to make things appear cool, they want to do it things differently and I fail to realize the point from business perspective.
I'm not doing it because thousands are though, I'm doing it simply for how easy it makes development, and how lesser prone to spaghetti I am.
I don't really know much about a business perspective beyond what I'm programming to be understood and worked on by everyone else independent of me. And while training new people on my project I've found them to appreciate little things like how you can log the output of every link in the chain to literally "time travel" through how your data transducing / logic is happening per step. If code in maintainable and people understand it, that's all that one really needs. Availability of talent is valid, tooling idk. But this is just in my case with the people around me, there could be cases where this paradigm is proving useless, mine isn't such.
But I'll say It's presumptuous and unnerving for you to say that everyone appreciates something they're doing because it's "cool". There's 200 other ways to have discourse about what you appreciate and what you do not that doesn't involve personal and presumptuous remarks!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I tried
Ramdaand I don't see the benefit of writing code differently, words likethousands of people are doing itdoesn't mean everyone else should do it.I am not saying it is bad, and again
scientific applicationswas an example, not an absolute statement, you have to evaluate what is best in terms of maintainability, availability of talent and tooling, and whether application really requires functional stuff or not.This is the biggest problem with developers today, to make things appear cool, they want to do it things differently and I fail to realize the point from business perspective.
I'm not doing it because thousands are though, I'm doing it simply for how easy it makes development, and how lesser prone to spaghetti I am.
I don't really know much about a business perspective beyond what I'm programming to be understood and worked on by everyone else independent of me. And while training new people on my project I've found them to appreciate little things like how you can log the output of every link in the chain to literally "time travel" through how your data transducing / logic is happening per step. If code in maintainable and people understand it, that's all that one really needs. Availability of talent is valid, tooling idk. But this is just in my case with the people around me, there could be cases where this paradigm is proving useless, mine isn't such.
But I'll say It's presumptuous and unnerving for you to say that everyone appreciates something they're doing because it's "cool". There's 200 other ways to have discourse about what you appreciate and what you do not that doesn't involve personal and presumptuous remarks!