11–18 of 18 posts
Earlier quoted context omitted.
[flagged]
no. if we use that framing of yours, fp aim is to write a solution that flows like a river while imperative solution is like rolling up a ball of various solutions and then throwing it at the problem.
I don't think functional programmers are necessarily more upset about AI being good at coding. If anything, FP tends to emphasize concepts that AI is already quite good at manipulating: composability, immutability, pure functions, and well-defined abstractions.
In other words, being a human expert in writing high quality implementations is less important now.
All of the years we've spent on immutable by default, strong types and dreaming about the lambda has to matter! The AI that just rips out thousands of lines an hour of imperative and weakly typed code just has to be leading organizations to ruin! You'll see!
We worked hard at honing our craft. It's still meaningful, damnit!
Earlier quoted context omitted.
no. if we use that framing of yours, fp aim is to write a solution that flows like a river while imperative solution is like rolling up a ball of various solutions and then throwing it at the problem.
The point is the details of the implementation don't matter that much anymore. It's just something for the AI to work out — much like assembly code generation is for compilers.
FP is disgusting looking anyway
Once React came out with shit like
useEffect(() => {}, [])
How the fuck does "useEffect(() => {}, [])" mean a function that will run when the page loads? And then if you do this
useEffect(handleComponentMount, [])
I know Haskell but use C++ as my daily tool. And I do care deeply about code quality because I don't want to spend most of my time fixing bugs.