News for hackers. Stuff that matters.
Re:Ace - Sinatra for Node with Fibers by kodablah on Tuesday February 14, 2012 @05:51PM (#3592172)
Might not be the best name for a JS lib/app since ACE is already a popular in-browser editor: http://ace.ajax.org/.

Also encouraging the use of node for synchronous processing (even when using coroutines) is unlikely to be high performing when scaled up. If you have work to do, it'd be best to defer to another service and let node work as a router.

Re:Ace - Sinatra for Node with Fibers by apaprocki on Tuesday February 14, 2012 @06:57PM (#3592352)
Not to mention the ACE C++ system, which has been around for years and is widely known: http://www.cs.wustl.edu/~schmidt/ACE.html
Re:Ace - Sinatra for Node with Fibers by olegp on Wednesday February 15, 2012 @04:07AM (#3593625)
I've run benchmarks comparing plain Node to Common Node (my library that uses fibers) and the version with fibers uses marginally more memory and on average has 75% of the throughput of the purely asynchronous code.

You can find the benchmarks and results in the project README: https://github.com/olegp/common-node#readme

Here are the graphs: http://www.slideshare.net/olegp/server-side-javascript-going...

Re:Ace - Sinatra for Node with Fibers by nyrb on Tuesday February 14, 2012 @06:25PM (#3592268)
+1 ACE Editor and Ace - Sinatra for Node might be confusing.

Maybe name it "Frank" (Frank Sinatra) or "Ray" (Ray Charles). :-)

Re:Ace - Sinatra for Node with Fibers by benatkin on Wednesday February 15, 2012 @12:42AM (#3593185)
Well, the creators of ace (macmann and mjackson) are lucky that ACE is almost always used as an acronym in the Ajax.org Cloud Editor's marketing and documentation. Because of this and the sheer number of JavaScript programmers out there, I think they'll most likely be able to keep the name.
Re:Ace - Sinatra for Node with Fibers by furtivefelon on Tuesday February 14, 2012 @07:07PM (#3592394)
very true, especially since node is single threaded, you might block other requests etc.