Live data from Hacker News

We open-sourced 90 node.js modules at Browserling

catonmat.net

31–35 of 35 posts

Re: We open-sourced 90 node.js modules at Browserling

#31
post #19

I know I'm getting to be a broken record, but two different attempts at an SSH server, neither of which work? Every other thing on this list is a reimplementation of something in Python's standard library or Twisted. I mean, yes, that's a lot of code to write, and I'm impressed, but this just feels like yet more reinvention of the wheel.

I think that's the point. Nodejs is a new technology and people are re-inventing all the Twisted (and other technologies like it) wheels so that you can use them from nodejs.

It's a Javascript interpreter/JITer/whatever. What is new about that?

Re: We open-sourced 90 node.js modules at Browserling

#33
post #7

James and Peteris are two of the most amazing devs I've seen in a long time. They ship and ship and ship and ship. The first version of StackVM (Browserling's underlying technology) was written in Haskell. They switched to Node close to two years ago if I'm not mistaken. I've gotten an early look at Testling, their cross browser testing web testing tools, and they're easily a year or two ahead of anyone else on the m…

They are amazing and Browserling is very handy, but they really need to hire a designer. A lot of their customers are going to be designers, there is no reason to have such a dated look.

It's all James's own artwork. Frankly, I love it.

Re: We open-sourced 90 node.js modules at Browserling

#34
post #31
post #19

Earlier quoted context omitted.

I think that's the point. Nodejs is a new technology and people are re-inventing all the Twisted (and other technologies like it) wheels so that you can use them from nodejs.

It's a Javascript interpreter/JITer/whatever. What is new about that?

It's a javascript environment that doesn't suck. Heyoooo!

Re: We open-sourced 90 node.js modules at Browserling

#35

Congrats! Incidentally, anyone have an idea how I can profile my Node app to see where I'm using up memory and CPU resources?

There are debugging, profiling and coverage tools though they're maybe not as well-developed as you'd like.

If you have any node questions, you should drop by the #node.js channel on freenode! It's a good place to get help and chat about asynchronous IO with (generally) friendly people.

Post reply on HN