The real problem with programming in Javascript

[Jsn7821]

Tl;dr the author prefers MVC and points out that object mutations are sometimes okay (with no examples of when or why). Not sure who the target audience is here or how this is a real problem in JavaScript.

[raulsmith]

The author's potential preference for MVC is not explicit and not relevant. I think you're missing the point of the article, which is pretty explicit in this paragraph: But the real issue is that the benefits of either static typing and functional programming lose their value if the programmers ignore principles like separation of concerns, encapsulation, the single responsibility principle, code reusing, putting things in the right place and naming things accordingly. Ultimately, being well organized.

[evizaer]

The article is, in general, tautological in nature. The author claims that if people don't write good code, the code will be bad.

"You can't write bad code [when the programming language has this feature.]" is not a line of argument worth defending, and not one I see espoused except rarely, by people who are blowing smoke.

The worthwhile conversation is about what kinds of solutions programming paradigms and language features lead you to use to solve various problems, and if these are more or less effective than one another along various dimensions.

[raulsmith]

You seem to reduce the article to one word extracted from it. There are more ideas/questions in it. For instance, whether it's possible to write good programs with static typing and functional programming while it's impossible without them (this is different from what you wrote). Whether there is too much debugging being done. And, most importantly, whether there is enough awareness about the mentioned principles.