Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IronNode – Debug Node.js code with Chrome Developer Tools

github.com

Post reply on HN
Print view View original

1–10 of 25 posts

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#5

Post by faceyspacey »

snarkyturtle wrote: post #3

How is this any different than: https://github.com/node-inspector/node-inspector

Node inspector has a lot of problems. Buggy as shit. And it's time consuming to use the -brk param to make ur app stop on the first line and then attach node inspector, and then switch back to having it not stop on line 1 when testing ongoing calls. That's why it is important what this guy built to automatically attach itself, even if all the other node inspector bugs still exist. It's particularly hard to find ur files in node inspector and with it refreshing ur always losing where u were, which is also a problem with chrome dev tools but to a lesser extent. I'm generally extremely surprised that node inspector is so shitty. Literally no node developers must debug server side code with a debugger. That's complete idiocy, ie resolving to just log calls throughout ur code. It's a statement of the lack of observability developers are willing to put up with because they know no better. I use node inspector constantly, but it's absolutely retarded how much bullshit I have to sift through. I have to reopen the files I'm working either every single time, drilling deep through file structures, if I don't already have a breakpoint on a file. It doesn't remember what files and folders were open.

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#8

Post by troebr »

faceyspacey wrote: post #5
snarkyturtle wrote: post #3

How is this any different than: https://github.com/node-inspector/node-inspector

Node inspector has a lot of problems. Buggy as shit. And it's time consuming to use the -brk param to make ur app stop on the first line and then attach node inspector, and then switch back to having it not stop on line 1 when testing ongoing calls. That's why it is important what this guy built to automatically attach itself, even if all the other node inspector bugs still exist. It's particularly hard to find ur fi…

Have you tried debugging with webstorm?

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#9

Post by richmarr »

josteink wrote: post #7

I thought the Iron* moniker was conventionally reserved for things running on .net (It Runs On Net), like IronPython, IronRuby, IronLisp, IronScheme, etc? Isn't using it for this project going to cause confusion?

I was going to make a snarky remark comparing it to the recent second usage of 'isomorphic' but, to be honest, people will figure it out. I'm putting all this stuff on my list of things not to waste blood pressure on.

Re: IronNode – Debug Node.js code with Chrome Developer Tools

#10

Post by josteink »

richmarr wrote: post #9
josteink wrote: post #7

I thought the Iron* moniker was conventionally reserved for things running on .net (It Runs On Net), like IronPython, IronRuby, IronLisp, IronScheme, etc? Isn't using it for this project going to cause confusion?

I was going to make a snarky remark comparing it to the recent second usage of 'isomorphic' but, to be honest, people will figure it out. I'm putting all this stuff on my list of things not to waste blood pressure on.

I was honestly trying to be helpful, and was definitely not making a snide remark. Sure, people wondering if this is node running on .Net might click and discover they were wrong, and all is fine.

But if his project from name alone is perceived as being related to .NET, he may not reach out to the full audience of web-developers he may be aiming for. And that's a net loss for him.

If there's a time to reconsider the name, it's now before it gets bigger and more "known". I mean the repo only has around 10 commits at this point :)

Post reply on HN