I think the fundamental flaw is: > It is considered good functional programming style to write functions in point-free form, omitting the unnecessary mention o

I think the fundamental flaw is: > It is considered good functional programming style to write functions in point-free form, omitting the unnecessary mention of variables (points) on which the function operates. This is wrong. It may be considered good programming style in certain small use-cases when a small local composition is clearer. But as a general software engineering principle, the exact opposite is true: It is considered good style to break larger constructs into smaller pieces and give them meaningful names. There's no reason that function parameters should be an exception to that and in practice, names for function parameters are often some of the most critical names for understanding a system. I think concatenative languages are really cool as a mental exercise in getting a lot of power out of something simple. But as far as why they aren't used in practice. I think it's largely because they are a bad idea carried to its logical extreme.