It would be nice to have a
warning when Node runs low
on stack when firing up (successfully at first glance). When
this happens and the first client logs in the client will just
hang there without any error on the server side.
Solution is to increase
On Mon, Jun 4, 2012 at 12:01 AM, Dean Mao dean...@gmail.com wrote:
Hm, I've never had issues with the ruby module system before -- it feels
somewhat similar to npm. I'm guessing quite a few ideas from npm were
derived from bundler/gems.
I think it's mostly related to bitnami having almost
That opinion is silly IMHO. Having an AMI ready to use in EC2 looks quite
useful. There is nothing that says how you have to use the components. You
can ignore any of them.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
True, but having used the bitnami ruby stack by mistake thinking it would
make ruby things easier, this has been a huge mistake. Though that might be
ruby's fault - god what an awful module system they have.
On Sun, Jun 3, 2012 at 2:21 PM, Mark Hahn m...@hahnca.com wrote:
That opinion is silly
Hm, I've never had issues with the ruby module system before -- it feels
somewhat similar to npm. I'm guessing quite a few ideas from npm were
derived from bundler/gems.
On any given system, I can untar one file and have node ruby running with
all my favorite packages via the home directory.
I would like to see a stack trace on uncaught exceptions. I thought the
node option --trace_exception did this but on a stack overflow I'm getting
only this in the exception object:
* uncaughtException
type*: string stack_overflow
message*: string Maximum call stack
