3 ms·
Similar story for me. Except that in 2010 I re-learnt JavaScript and discovered how beautiful, flexible and powerful it can be as a client side / server side la
by factorialboy 14y ago
Similar story for me. Except that in 2010 I re-learnt JavaScript and discovered how beautiful, flexible and powerful it can be as a client side / server side language
- jmspring 14y agoI've been node'n it up a bit myself lately. The language is easy to write, pretty easy to get things done, and server-side node provides a lot of great libraries. That said, the development ecosystem around Javascript is very immature. To really write decent amounts of server-side JS as a team, people often employ linters and other things to sanity check their code. Debugging? Mostly printf's (or equivalent). Scoping rules can also be pretty annoying. It is useful for getting things done, but it generally isn't my first choice (at least server side).
- AdrianRossouw 14y agoHave you not seen [1] node-inspector? It allows you to debug your server side code with the chrome/safari web inspector. [1] https://github.com/dannycoates/node-inspector https://github.com/dannycoates/node-inspector
- jmspring 14y agoAdrian - I have and it is a very useful tool. I guess my main gripe is the fact that the tool set is there in some form, but each has its area and none of them are really connected/integrated. I suspect the toolchain will eventually get there, but it is a big step back if one is used to more integrated ecosystems.