If this continues, we will never approach a set of tools that comfortably expresses human ideas. Instead we will remain lost in low-level implementation. We will never come to agreement about the goals and concepts that should be represented and readable at the high and intermediate levels of any application.
What is the solution? It really doesn't take new tools.
What we need is for every programmer to focus on summarizing their applications purpose and structure in a brief, explanatory, comprehensible fashion, at the top, and to use that to drive the actual implementation through a set of similarly comprehensible intermediate structures, until the application works, and is modifiable at any of these levels, by any person.
We've stopped looking at programs as examples of beautiful communications among software engineers. We need to focus on making them comprehensible from the top, and never stray from it. Unfortunately, we do stray from comprehensibility all the time, for expediency, or to follow some technical pattern, or conceptual orientation, or framework ideology, or logical consistency, or other fashionable nonsense.
Don't do it. When you read those newly-learned, initially-incomprehensible sets of statements or language features, or dorky framework requirements, consider them less central than their designers do. They aren't your program. Push them down into some kind of container for details ... an object or a function or whatever ... and make sure it takes over the readability of the operational top of your program, or any of the intermediate levels after that.