A typical Angular app is a veritable sea of Singletons ie. Stateful Services.

A typical Angular app is a veritable sea of Singletons ie. Stateful Services.

Sometimes it feels as if the Angular team decided to collect together all the world’s worst programming patterns and a put them into one convenient framework.

Originally shared by mathew murphy

Many people have expressed the opinion that singletons are a code smell. Now someone has looked at codebases to quantify to what extent that’s true.

https://blog.ndepend.com/singleton-design-pattern-impact-quantified/

I seriously don’t have a dog in this fight.

I seriously don’t have a dog in this fight. Some people really despise NodeJS as a production level server. I’m interested to know why.

I mean Node runs a scripting language like Ruby or PHP but is superior in performance to those systems because of its non-blocking architecture. Naturally being interpreted it can’t be as fast as a compiled language such as Go or Java.

So this is an open thread asking why you wouldn’t use it in production? Note that “because it’s JavaScript” is not an argument that is going to carry any water around here. JavaScript performance from the point of view of an interpreted language is already pretty good relative your favourite scripting language X so let’s get down non-bullshit arguments about why it’s bad.

https://medium.com/javascript-scene/introduction-to-node-express-90c431f9e6fd

Eric Elliott takes a hard line on JavaScript’s “new”, “instanceof” and “class” keywords.

Eric Elliott takes a hard line on JavaScript’s “new”, “instanceof” and “class” keywords. In a nutshell, don’t use them.

In their place he suggests object factory functions which still create objects but do it via Object.create().

JavaScript: “the good parts” remains a small subset of the full language.

https://medium.com/javascript-scene/javascript-factory-functions-vs-constructor-functions-vs-classes-2f22ceddf33e