Hacker Newsnew | past | comments | ask | show | jobs | submit | BrianHammond's commentslogin


    _ry: fictorial: eventually, not for 0.2
http://nodejs.debuggable.com/2010-05-07.txt


For those using Node.js, the same is

    var len = Buffer.byteLength(a_string, 'utf8')


I enjoy TheSansMonoCd by LucasFonts. It costs money though.

http://imgur.com/kBpMI.png


http://steveblock.com/r/sgiscreen-ttf.tar.gz

Looks pretty good at 14pt in Terminal.app. Thanks.


WebGL is mentioned on that page. I'm not sure if it was updated since you looked.

"Conclusion: Not ready*. Waiting for Internet Explorer 8, Firefox 3.6, Chrome 4, Opera 10.5 to expire"


"This can get sloppy."

Indeed it can. I am a fan of flow-js however. It has really helped me to avoid getting sloppy in Node.js.

http://github.com/willconant/flow-js


The big question is if Heroku will suddenly support a fairly large number of long-lived connections to a Node.js hosted app, and how pricing would work. Developing real-time apps and custom servers are how Node.js really shines. A WebSockets module took only a few hours to develop for instance.


Thanks for the shout-out in the slides about the Redis client for Node.js.

http://github.com/fictorial/redis-node-client


I'm curious about the "fanout" name which immediately made me think of a message broker like RabbitMQ on the backend somewhere. I guess "fanout" here means 1 client to fanout.js to N >> 1 other clients.

There are a number of similar projects popping up like this one as of late for Node.js. NodeRed, fanout, dealer, etc.

That's great. Node.js makes previously "complex" things a little easier to setup and play with.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: