Note: I wrote this blog on request
Fragmented implementation and lack of standardization
asm.js based application much faster.
- not to use
undefinedrather use static types,
- to avoid arrays of varying types,
- finally to use less constructors and initialize all the variables in the constructors.
The poor coding can be identified by some static analysis. And these tools can be integrated in the IDE and browser. This way the programmers get notified of the performance issues.
Frameworks are the right way
- jquery(It is more like library than a framework with easy-to-use API with a lot of open-source modules),
Some of them are domain specific and some are for general use. These frameworks feature popular programming patterns for object based language. They allow us to use those well-written patterns. It makes the user code small. It is like “write less do more”. Less code gives less bugs and may be less performance hazards. In that sense less is good. Again these frameworks allow us to write browser independent code. These frameworks also take advantage of the ahead of time compilation. This is why they are immensely popular.
A note on nodeJS
But sometimes I get back to C for some reason. I discovered that my framework written in C also support doing cool things with small dependable code. I think my compiled-framework gave me greater understanding of cool stuff in C.