I've done a fair amount of messing around with javascript.
1. Recompiled webkit into javascript using emscripten/asm.js (webkit.js)
2. Created a desktop version of node (tint2) using FFI calls for OSX/Windows
3. Reconstructed much of the oracle o5login/tns/tti protocol for giggles (and if you want to see a very head scratching way of packing 64 bit signed ints, look no further than 11g).
What I can say is it isn't perfect. But it has one gigantic advantage is you don't need to build or compile to run, but still get nearly the same performance from compile time languages.
It's a near perfect prototyping language, and for most peoples use (e.g., 99% of crud/general business humdrum logic) it's perfectly fine.
Just stay away from relying on too many npm modules.
1. Recompiled webkit into javascript using emscripten/asm.js (webkit.js) 2. Created a desktop version of node (tint2) using FFI calls for OSX/Windows 3. Reconstructed much of the oracle o5login/tns/tti protocol for giggles (and if you want to see a very head scratching way of packing 64 bit signed ints, look no further than 11g).
What I can say is it isn't perfect. But it has one gigantic advantage is you don't need to build or compile to run, but still get nearly the same performance from compile time languages.
It's a near perfect prototyping language, and for most peoples use (e.g., 99% of crud/general business humdrum logic) it's perfectly fine.
Just stay away from relying on too many npm modules.