That is actually currently being contested by React and .jsx.
That said, I've seen multiline abused for writing SQL queries as well, which would have been better off being written in a separate .SQL file and `fs.read` into a string with a descriptive var name. (Ignoring that massive SQL strings is a code smell imo).
Except if your application generates dynamic queries. And not of the sort where variables in the WHERE clause are dynamically evaluated. Of the sort where the entire structure of your SQL is dynamically driven by user interaction with your application.
Are you saying that large SQL strings isn't a code smell if the application is dynamically putting them together? That seems like DSL/Query Builder territory to me. Perhaps you could share an example?
IMO Haskell is your best option if you want to learn functional programming (being a purely functional language) and this is the best guide to learning Haskell I've come across: https://github.com/bitemyapp/learnhaskell
It also has an irc channel that is fairly active (#haskell-beginners).
To bolster this argument. I made my consulting money off coming in to fix projects that had been churned out like this. The issue is real enough to warrant good money to fix.
It will be based on the idiom "forest for the trees", effectively having the same meaning but also includes the fact that they are a part of what makes up the forest.
