4 ms·
Using javascript as a main language for large projects is bad idea, let alone node.js. In browser environment at least you can use debugger, while on server sid
by dotborg 14y ago
Using javascript as a main language for large projects is bad idea, let alone node.js. In browser environment at least you can use debugger, while on server side using any of available js interpreters/compilers is a black box just like rails/php/django etc.
Javascript is a scripting language and on server side it should be used like this.. scripting language, small and independent pieces of code, not a 100kloc+ "OOP" clusterfuck :)
- cjbprime 14y agoYou can use the browser's debugger to attach to a nodejs process: https://github.com/dannycoates/node-inspector https://github.com/dannycoates/node-inspector
- dotborg 14y agothat's very cool! not sure if it's production ready, should my business depend on some weekend projects posted on github?
- neya 14y agoI second your comment, it's a very valid concern.
- ricardobeat 14y agoI wish my weekend projects had +100 forks and thousands of developers bookmarking it...
- dancryer 14y agoI'd suggest if that is your attitude towards github projects, perhaps any development involving open source projects isn't for you...?
- ricardobeat 14y agoNode's philosophy is exactly that: small and independent services that together make an application. If you want a huge monolithic codebase definitely avoid node. The "script" in javascript doesn't make it any less of a programming language (it was a marketing play on Java), and in some ways it is more powerful than many others. Debugging is the same as debugging any other server-side language, and you're only worried about your application code; V8 is a very stable project, you're not going to find yourself debugging the interpreter.