It's ironic that the illustration for JavaScript is probably the most realistic and best solution IRL. In the sense that a lot of what problem solving is (which is a big part of software engineer) is breaking a big problem into smaller problems. And you continue doing this until each problem is solvable in a short period of time.
You're completely correct. But what I meant by that graphic is "poor solutions leading to more problems", not "breaking down problems into smaller ones". It was inspired by a cube drone comic that made the same complaint, but I can't find that particular comic now
I guess I have to defend this one. I personally think Typescript is the better language compared to typed Python or Ruby (two comparable languages based on how they are all used). Modern Javascript actually have a lot of nice language features, the only issue is the lack of types. Typescript doesn't entirely solve the problem but it's a decent attempt at it. A good typescript repo is decently readable, testable and performant enough for most use cases.
Typescript is wasted on JS. Currently getting a JS certification while porting an action script 3 project to JS, ActionScript 3 was the better language.
I dunno we run and service serval large application running with React TS as the client with C# Entity Framework for the Server with SQL and wrapped up nicely in GraphQL.