It's probably a good idea to remove unnecessary baggage along the way.
Hi,
I have also an issue with node-gyp in my project since I moved from node
version 0.6.x to 0.8.2
I had to move my 'ycore' directory and change the path in 'dependencies'
removing '../' :
used to be
'dependencies': [
'libyapplication',
*'../ycore/binding.gyp:ycore',*
* *],
now
I'm getting a vibe that no one thinks this is actually a need and wondering
where my perception is skewed. In systems I worked on, we could not control
all the modules we were using and make them support pluggable logging. I'm
also wondering if this makes sense as the best practice since I
GLOBAL and root are the relics. Are there any actively maintained
modules that still use them? Is there any way to get this kind of data from
npm?
On Thursday, July 12, 2012 4:12:19 PM UTC+2, Tim Caswell wrote:
On Thu, Jul 12, 2012 at 1:22 AM, Joran Greef jo...@ronomon.com wrote:
It's
Let's face it, some globals are convenient :p otherwise hell,
require('array'), require('object'), require('array-map')... the list
goes on
On Jul 11, 8:40 am, Joran Greef jo...@ronomon.com wrote:
I noticed that running an empty node interpreter always provides these
global variables:
require
In my experience most libraries don't even bother logging anything, and so
all logging ends up being custom, giving you full control over it. What are
you using that logs that you can't customise?
On Thu, Jul 12, 2012 at 10:21 AM, Elad Ben-Israel
elad.benisr...@gmail.comwrote:
I'm getting a
Yeah, at least one or require('require') won't work :-P
On 12/07/2012, at 17:28, tjholowaychuk wrote:
Let's face it, some globals are convenient :p otherwise hell,
require('array'), require('object'), require('array-map')... the list
goes on
On Jul 11, 8:40 am, Joran Greef
On Thu, Jul 12, 2012 at 7:12 AM, Tim Caswell t...@creationix.com wrote:
On Thu, Jul 12, 2012 at 1:22 AM, Joran Greef jo...@ronomon.com wrote:
It's probably a good idea to remove unnecessary baggage along the way.
It's also a good idea to not break people's code without good reason.
The
// test.js
var i=0;
debugger;
// node debug test.js
// n(next)
// backtrace= #0 test.js:2:1
// i = i not defined
how to display the value of i?
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
http://nodejs.org/api/debugger.html
repl
i
On 07/12/2012 10:47 AM, josh wrote:
// test.js
var i=0;
debugger;
// node debug test.js
// n(next)
// backtrace= #0 test.js:2:1
// i = i not defined
how to display the value of i?
--
Job Board:
Hi,
This question is bit off topic.
Im from a company where we build some cloud based tools for a
local telecommunication providers.
Basically we are building developer tools which reside on the cloud.
I need to convince my management to allocate resources for realtime web
technologies.
First you should probably convince us why you need real-time technology.
If you want reasons to use node, then this topic has come up before. Some
common
reasons are:
- Node has a great community that attracts lots of smart people
- Which leads on to `npm` and how node has sane package
did you run make clean before trying with --without-snapshots ?
I had a build problem (older g++ version) and it didn't compile v8.1. but
compiles v8.2 great with the --without-snapshots flag.
On Wednesday, July 11, 2012 6:46:45 PM UTC-4, Michael Smith wrote:
On Wednesday, July 11, 2012
Hi Arunoda,
Firstly, you need to look at your application, and what it does. If it's user
facing, like a social network, then – if it's done right – realtime web:
- increases user engagement
- increases visitor pageview time (users spend more time looking at
the
Hi all,
Just for curiosity, who's using Emacs in here to code arround Node?
What modes do you use, what configurations?
--
RMA.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you
Nodetime seems very cool.
http://nodetime.com/
Den onsdagen den 11:e juli 2012 kl. 22:41:19 UTC+2 skrev Gustavo Machado:
Hi,
Does anyone know of any analytics modules for node.js web servers? More
specifically to analyze the traffic on an expressjs application.
Thanks,
Gus
--
Job
Nuno,
I think that Google Analytics is more suitable for client side analytics.
What if what I host with express.js has a REST API? I need something that
tells me how many times each endpoint has been called, the time it took,
the response status code, etc.
Ideally, store all this information in
redis is great for this sort of thing if you want to roll your own,
we instrument lots of our codebase with simple fire-and-forgets like:
stats.incr('login')
On Jul 11, 1:41 pm, Gustavo Machado machad...@gmail.com wrote:
Hi,
Does anyone know of any analytics modules for node.js web servers?
Why not just do analysis on your log files? Or record specific data to
statsd/graphite,
eg, counts on status codes returned?
I do something like this:
- response time (timer)
- response status codes (count)
- hits per pathname (count)
So, I have keys in statsd like:
Emacs is my tool of choice most of my development work especially node.js,
javascript, markdown, etc.
I use Aquamacs when on OS X and gnu emacs when running linux.
Some of my favorite modes/packages are:
- js3.el mode https://github.com/thomblake/js3-mode
- jshint mode - slightly patched
I use js2-mode, yasnippets with https://github.com/azer/js-yasnippets
On Thu, Jul 12, 2012 at 9:06 AM, Jeff Barczewski
jeff.barczew...@gmail.com wrote:
Emacs is my tool of choice most of my development work especially node.js,
javascript, markdown, etc.
I use Aquamacs when on OS X and gnu
Hi again,
I removed all unnecessary methods like all logging handling and renamed
some methods. Here is a shorter example which is much more powerful than
the current domain module:
var scope = require('error'); //my module
scope.addErrorListener([Error], function (err, next) {
@Tim Yeah! I did a bad job to convince you. Thank you for posting previous
post on Node. That is helpful.
@Patrick. I've gone through it. I was a good one for node. Thanks.
@Micheil your point clear me out.
If it is a user engaging platform, real-time looks good.
And the benefits you've shown is
Just as a data point, we depend heavily on websockets for c9.io. It's
an online IDE written in node. We need realtime feedback for
breakpoint debugging sessions, terminal emulators in the browser,
pushing various events to the browser (file change events) and
collaborative editing.
While the
This is OT for the node-dev list. Please post these sorts of things
to nodejs@googlegroups.com. Thanks.
On Thu, Jul 12, 2012 at 4:02 AM, Christian Taltas christ...@yupana.com wrote:
Hi,
I have also an issue with node-gyp in my project since I moved from node
version 0.6.x to 0.8.2
I had
Yes. I got it.
C9 story is just looks bit familiar to us.
We can do a better job with websockets.
I can use c9 story as a reference. Thanks.
On Thu, Jul 12, 2012 at 10:51 PM, Tim Caswell t...@creationix.com wrote:
Just as a data point, we depend heavily on websockets for c9.io. It's
an
A node process in production died abruptly and this appeared on the
console...
node: /root/.nvm/v0.6.12/include/node/node_object_wrap.h:62: void
node::ObjectWrap::Wrap(v8::Handlev8::Object): Assertion
`handle-InternalFieldCount() 0' failed.
Is this a bug in node. Should I file an issue?
Now
Awesome!!! Thanks for making the binaries available!
On Tuesday, July 10, 2012 9:13:41 PM UTC-4, Geoff Flarity wrote:
FYI, I've created a github page with links to a binary and build
instructions for getting Node to run on the Raspberry Pi:
https://github.com/gflarity/node_pi
It takes
On Jul 12, 1:40 pm, Mark Hahn m...@hahnca.com wrote:
A node process in production died abruptly and this appeared on the
console...
Out of curiousity, what compiled node addons (if any) are you using?
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
It was a vanilla install from NVM.
On Thu, Jul 12, 2012 at 10:52 AM, mscdex msc...@gmail.com wrote:
On Jul 12, 1:40 pm, Mark Hahn m...@hahnca.com wrote:
A node process in production died abruptly and this appeared on the
console...
Out of curiousity, what compiled node addons (if any) are
this may take your interest; http://github.com/azer/onejs
azer
On Wed, Jul 11, 2012 at 3:31 PM, Marcel Laverdet mar...@laverdet.com wrote:
Too robust is not a thing. This is a problem that is very complex. As
mentioned in later replies by the Caja team and others since node is using a
very
On Thu, Jul 12, 2012 at 7:40 PM, Mark Hahn m...@hahnca.com wrote:
A node process in production died abruptly and this appeared on the
console...
node: /root/.nvm/v0.6.12/include/node/node_object_wrap.h:62: void
node::ObjectWrap::Wrap(v8::Handlev8::Object): Assertion
I could have swore I *just* saw a project that exposes the Stream API to
the browser so that you can use things like `event-stream` on the
browser to communicate with the server. It looked like it came out of
NodeConf. I even think I bookmarked it.
Or was it all a dream?
--
Alan Gutierrez -
Only if it happens with 0.6.20
So I can't file bug reports for 0.8.1? I thought 0.8.x was stable. What
is special about 0.6.20? Do I have to go back to 0.6.20 to get support?
The problem just happened again. I just bumped my production server to
0.8.2 on the off-chance the problem is unique
I believe Mr. Noordhuis misread your nvm output and thought you were
running 0.6.18 (the other version you seem to have installed)
I would say try 0.8.2 and if that fails, then file an issue.
On Thu, Jul 12, 2012 at 12:59 PM, Mark Hahn m...@hahnca.com wrote:
Only if it happens with 0.6.20
Hi nodejs group,
Any suggestions for drop-in enhancements/replacements to EventEmitter which
allow events to
replicate cross-process or across different systems?
Bonus points for anything that supports multiple transports!
-rektide
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
Here's my .emacs.d https://github.com/medikoo/emacs-starter
I don't use anything Node specific, just slightly modified js2-mode for
highlighting js and json files.
On Thursday, July 12, 2012 2:59:25 PM UTC+2, Mihamina Rakotomandimby wrote:
Hi all,
Just for curiosity, who's using Emacs in
Is there any plan to implement a worker thread API for node similar to the
W3C spec?
http://www.w3.org/TR/workers/
I see that there are third party implementations of this API, but I'm
wondering if something like this will end up in the core node distribution.
--
Job Board:
I'd love to see this, but then, I was also hoping to see isolates, and was
imaginging a
perfect fusion of the two. I don't believe there's any plan for either.
Background on isolates:
https://groups.google.com/forum/?fromgroups#!msg/nodejs/zLzuo292hX0/F7gqfUiKi2sJ
On Thu, Jul 12, 2012 at
https://github.com/hookio/hook.io
On Thu, Jul 12, 2012 at 4:07 PM, rektide rekt...@voodoowarez.com wrote:
Hi nodejs group,
Any suggestions for drop-in enhancements/replacements to EventEmitter
which allow events to
replicate cross-process or across different systems?
Bonus points for
On Thursday, July 12, 2012 5:59:25 AM UTC-7, Mihamina Rakotomandimby wrote:
Hi all,
Just for curiosity, who's using Emacs in here to code arround Node?
What modes do you use, what configurations?
I use mooz's fork of js2-mode. https://github.com/mooz/js2-mode
Mooz's fork fixes a
-- Forwarded message --
From: Don Armstrong d...@debian.org
Date: Thu, Jul 12, 2012 at 8:59 PM
Subject: [CTTE #614907] Resolution of node/nodejs conflict
To: debian-devel-annou...@lists.debian.org
=== Resolution ===
The Technical Committee reaffirms the importance of preventing
Wow, the debian community sounds kinda scary. I'm definitely not used
to these sort of top-down edicts. Is it just me?
--Josh
On Thu, Jul 12, 2012 at 2:41 PM, Carl Fürstenberg azat...@gmail.com wrote:
-- Forwarded message --
From: Don Armstrong d...@debian.org
Date: Thu, Jul
I’ve always thought “node” was WAY too generic of a name for the binary.
“nodejs” is both more recognizeable out-of-context and more consistent
with node.js’s own branding.
-FG
On 12.7.12 4:46 PM, Joshua Holbrook wrote:
Wow, the debian community sounds kinda scary. I'm definitely not used
to
On Jul 12, 4:35 pm, Brendan Miller catph...@catphive.net wrote:
Is there any plan to implement a worker thread API for node similar to the
W3C spec?http://www.w3.org/TR/workers/
There was at least one [1], but it doesn't seem to be maintained
anymore.
[1]
On Jul 12, 4:35 pm, Brendan Miller catph...@catphive.net wrote:
I see that there are third party implementations of this API, but I'm
wondering if something like this will end up in the core node distribution.
Doubtful, since there is already the child_process and/or cluster
module.
--
Job
Finally, a triumph of process and committee over usability.
Well done. *slow clap*
-Mikeal
On Jul 12, 2012, at July 12, 20122:41 PM, Carl Fürstenberg wrote:
-- Forwarded message --
From: Don Armstrong d...@debian.org
Date: Thu, Jul 12, 2012 at 8:59 PM
Subject: [CTTE
Well the resolution is a little unfortunate, but it's a good compromise for
both package I feel.
On Thu, Jul 12, 2012 at 2:49 PM, Felipe Gasper fel...@felipegasper.comwrote:
I’ve always thought “node” was WAY too generic of a name for the binary.
“nodejs” is both more recognizeable
Hi, I'm a bit new here, I have in mind to make a real-time application on
that involve money and bank accounts, and was thinking of using Node.js +
Express + Now.js any SQL database or NoSQL, the problem I have no
information on how safe or good is Node in this field, any of you have used
https://github.com/maxogden/domnode is probably what you're thinking of.
On 12 July 2012 11:58, Alan Gutierrez a...@prettyrobots.com wrote:
I could have swore I *just* saw a project that exposes the Stream API to
the browser so that you can use things like `event-stream` on the
browser to
I wrote a simple test of nested domains which looks like this:
var topDomain = domain.create();
var subDomain = domain.create();
topDomain.add(subDomain);
topDomain.on(error, function(err) {
console.log(Top saw an error: + err.message);
});
subDomain.on(error, function(err) {
On Thu, Jul 12, 2012 at 9:22 PM, Addison Higham addis...@gmail.com wrote:
I believe Mr. Noordhuis misread your nvm output and thought you were running
0.6.18 (the other version you seem to have installed)
I would say try 0.8.2 and if that fails, then file an issue.
That's indeed what I meant.
When it comes to finance, SQL comes out on top - things like MySQL have been
battle tested for decades, accounts information is intrinsicly relational so
relational databases are the right fit, ACID compliance with nosql is more
liberal but with your project you'd need 100% reliability.
Also
I assume we can all move on and ignore this.
On Thu, Jul 12, 2012 at 2:52 PM, Mikeal Rogers mikeal.rog...@gmail.comwrote:
Finally, a triumph of process and committee over usability.
Well done. *slow clap*
-Mikeal
On Jul 12, 2012, at July 12, 20122:41 PM, Carl Fürstenberg wrote:
Thanks to all. I should have understood what @Noordhuis meant. I'm on
0.8.2 now and hopefully we will never hear of this again. If it happens
again I'll jump back to 0.6.20 and do whatever I can to help find the
problem with 0.8.x.
On Thu, Jul 12, 2012 at 3:19 PM, Ben Noordhuis
I mean, at some point someone's gonna ask why all the scripts with
#!/usr/bin/env node don't work at some point in the future, and we're
gonna have a big thread about whether Deblian made the right choice
and how everyone on linux should just compile from source anyway.
Might as well cross that
What was the other node that conflicted?
On Thu, Jul 12, 2012 at 4:00 PM, Joshua Holbrook josh.holbr...@gmail.comwrote:
I mean, at some point someone's gonna ask why all the scripts with
#!/usr/bin/env node don't work at some point in the future, and we're
gonna have a big thread about
So they have chosen who gets to use what name? That is insane. It will
never work. There will be web pages for the rest of time telling how to
fix a node installation on debian.
I'm new to the linux community. Has this been tried before, and did it
work?
On Thu, Jul 12, 2012 at 4:15 PM, Ian
https://github.com/nodejitsu/nssocket/
On Thu, Jul 12, 2012 at 10:50 PM, Matt hel...@gmail.com wrote:
https://github.com/hookio/hook.io
On Thu, Jul 12, 2012 at 4:07 PM, rektide rekt...@voodoowarez.com wrote:
Hi nodejs group,
Any suggestions for drop-in enhancements/replacements to
If you want multi-transport, freestyle rpc (with callbacks), then
dnode-protocol (by substack) or smith (by me) are nice.
https://github.com/substack/dnode-protocol/
https://github.com/c9/smith
On Thu, Jul 12, 2012 at 7:07 PM, Oliver Leics oliver.le...@gmail.com wrote:
I'm new to this sort of edict.
After reading http://bugs.debian.org/614907, is saying fuck you
an appropriate response? Serious question.
My favorite part, is when the debian developers start accusing each other
of clandestinely working with the node core team to run crying to the
techinical
Glorious! So say we all!
`node` for all!
On Thu, Jul 12, 2012 at 11:41:39PM +0200, Carl Fürstenberg wrote:
-- Forwarded message --
From: Don Armstrong d...@debian.org
Date: Thu, Jul 12, 2012 at 8:59 PM
Subject: [CTTE #614907] Resolution of node/nodejs conflict
To:
There are rumors that current Node.js (or, more exactly V8 GC) performs
badly when there are lots of JS objects and memory used.
Can You please explain what exatly is the problem - lots of objects or lots
of properties on one object (or array)?
Maybe there are some benchmarks, would be
When you have highly structured data with high levels of interdependence,
such as lots of numbers that all depend upon one another - i.e bank
accounts - you use SQL.
When you have fairly unstructured, loose data that is fairly independent,
such as content - i.e you are building a blog or another
On Fri, Jul 13, 2012 at 3:10 AM, Alexey Petrushin
alexey.petrus...@gmail.com wrote:
There are rumors that current Node.js (or, more exactly V8 GC) performs
badly when there are lots of JS objects and memory used.
Can You please explain what exatly is the problem - lots of objects or lots
of
I am not familiar with Debian or Linux, but am a manager of the MacPorts
project, and in that capacity I have certainly encountered the problem of two
different software packages wanting to install a program of the same name. The
authors of those software packages might not have been aware of
Also, you could implement the Stream API in the browser on your own, or use
browserify, and you'll get it for free. The Stream API still requires
implementation if you want to use it, but I get excited about the prospect
of the Stream API moving to the browser. =) I touched on the idea during my
On 12.7.12 9:52 PM, Ryan Schmidt wrote:
What would speak against officially renaming the node binary to
nodejs? I understand the reluctance to make changes for no reason,
but this change would have a reason: it would fix the name collision,
and would make the program name less generic and more
I understand the sentiment, but after all the hullabaloo surrounding
fs.exists/path.exists and require('sys')/require('util') I don't
really want to change /anything/. I'd rather deal with the confused
debian users than make more changes due to being the right thing.
--Josh
On Thu, Jul 12, 2012
On Thu, Jul 12, 2012 at 01:38:02PM -0700, Andrew Lunny wrote:
On 12 July 2012 11:58, Alan Gutierrez a...@prettyrobots.com wrote:
I could have swore I *just* saw a project that exposes the Stream API to
the browser so that you can use things like `event-stream` on the
browser to
Hi all,
I have a concern when using pubsub mechanism of redis in my real application.
I built a MMO game with 5 servers (NodeJs) and use pubsub of Redis to
broadcast game state between servers.
But I concern which is the best practice to utilize this mechanism
efficiently with a lot of users
Hello,
I would definitely recommend just adding one listener and doing all your routing
from there. Something like:
redis.subscribe('channel1')
redis.subscribe('channel2')
redis.on('message', function (channel, message) {
// emitter.emit(channel, message)
//
// -or
Thanks Tim for your suggestion about subscriber part.
Any suggestions for publisher part(one publisher for each ACTION or one
publisher for ALL ACTION)? I want to hear about it.
Thanks.
On Fri, Jul 13, 2012 at 12:07 PM, Tim Smart t...@fostle.com wrote:
Hello,
I would definitely recommend
The `npm install redis` client has a (very generalised) throughput of around 50k
messages per second. If you think that will be a ceiling for you, then client
pooling might become an option.
Another alternative is a redis client I made that can roughly double the
performance for small messages.
In your case if you are just publishing strings/numbers, creating some
network of channels by name could be useful. If you are publishing a
stringified json object, its probably not necessary to also use
different subscription channels because that data can be part of what
you send but you could
75 matches
Mail list logo
