4 ms·
This somewhat annoys me. "Knowing what you are doing" is time efficient. Regardless of what tooling you have.
by taeric 5y ago
This somewhat annoys me. "Knowing what you are doing" is time efficient. Regardless of what tooling you have.
- brightball 5y agoThe flip side is maintainability, which gets much simpler long term with FP.
- taeric 5y agoDo you have evidence showing this? The few long term maintained programs I am aware of are decidedly not what one would call modern functional. (Granted, the most ported and maintained software I know of is either Linux or SCUMM.)
- hvs 5y agoThis is a statement that requires some sort of citation. Extraordinary claims and all that.
- brightball 5y ago20 years experience with OO code. Over time, OO always leads to entanglement due to inheritance based solutions that seemed like a good idea at the time. Eventually, these become the basis for many other parts of the system. You combine the potential for side effects in the code with a tree that can't easily be changed because of how many other things it will negatively affect and you end up with a code base that is harder and harder to change the larger it gets. In a FP approach, this is a class of problems that you can't easily replicate. Yes there's a learning curve to operating in a FP style, but once you're able to move quickly with it the long term rewards are a byproduct. The OO solution to avoiding this problem is to build with microservices instead, which forces different parts of the system to be isolated and minimizes the negative effects from entanglement...but microservices come with their own maintenance and speed of development headaches as well.
- mbrodersen 5y ago35 years of OO experience here. Maintaining very large C++ code bases. I never have OO entanglement problems due to inheritance based solutions. Why? Because I only use inheritance for interfaces. Nothing else.
- wyager 5y agoI know what I’m doing in many languages, and I’m uniformly more productive with the FP ones. The only time I’ll reach for a non-FP language is if I’m forced to for work or if I’m working on an embedded system with no allocator.
- taeric 5y agoIs this confirmation/survivor bias, though? I would love to know that there is a panacea that automatically improves productivity. Unfortunately, I haven't seen one in my career, as yet. I am certainly more happy in many functional languages. And I can see happiness contributing to some. But I can't count that as data, without RCTs or something similar. I'm not going to go so far as to claim that computer science isn't science. But I do fear that there are more claims than there are checks in our industry.
- wyager 5y agoI wouldn’t say it “automatically improves productivity” - I suspect it might be limited to more intelligent and/or mathematically inclined programmers. That said, I think for many programmers not using it is a huge and pointless missed opportunity. This is one of those visibly high-return arbitrages that it pains me to see go unexploited.
- taeric 5y agoI certainly don't want my criticism to be a call to avoid functional programming. I just get an uneasy feeling when I see it over sold, as well.
- js4ever 5y ago"mathematically inclined programmers." This kind of programmers are literally the worst I met in 25 years of carreer. They are underperforming very badly compared to others.
- wyager 5y ago