nodejs Google Group

Re: [nodejs] Module naming

marco.rog...@gmail.com (Marco Rogers) — Sat, 25 May 2013 22:06:25 UT

It's not clear from this thread what you want exactly. You want to name
your modules whatever you want, not use namespaces, have them on npm, and
also avoid name collision? How exactly do you see that working?

Re: [nodejs] Module naming

gsta...@gmail.com (George Stagas) — Sat, 25 May 2013 18:06:28 UT

2013/5/25 Alex Kocharin <a...@equenext.com>:

They're both public data containers that you upload stuff into. One
has a single namespace, the other has a username-based namespace.
What's for "deployment" and what's for "development" are purely
personal choices.

Incorrect column offsets in stack trace for minified code

per.roveg...@factor10.com — Sat, 25 May 2013 17:41:41 UT

Hi,
I have the following minified script code:
var start=function(){function n(n){return n.length}function t(t){return
42+n(t)}function r(n){return t(n.x)}function u(n){return r(n)}return
u}();start({x:null});
It's 163 characters long. When I run it with Node version 0.10.8, I get the
following stack trace:

Re: [nodejs] Is there other ways to improve node.js performance

capt...@hacksparrow.com (Hack Sparrow) — Sat, 25 May 2013 17:39:13 UT

The cluster API provides an easier interface for working with multiple
processes for your app. And you can get the best out of Node by placing a
reverse proxy like nginx infront of it. Let nginx handle everything it can,
that includes gzipping, serving static files etc. Use Node only for
processing dynamic requests.

Re: [nodejs] Module naming

a...@equenext.com (Alex Kocharin) — Sat, 25 May 2013 17:38:22 UT

should be given equal chance of discovery though.
Github is a tool for development, npm registry is a tool for deployment. Am
I missing something here? By the way, mix of those two is very well known
to create serious trouble ([link]).
Also, there was a holywar in npm issues about namespacing... I guess

Re: [nodejs] Module naming

gsta...@gmail.com (George Stagas) — Sat, 25 May 2013 15:49:36 UT

2013/5/25 Alex Kocharin <a...@equenext.com>:

I want both visibility and proper naming. That logic isn't valid.
Github is very public. We just need to find a way to index these along
with the rest npm modules. Whoever likes can publish to npm, whoever
likes can push to Github. Both should be given equal chance of

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

a...@equenext.com (Alex Kocharin) — Sat, 25 May 2013 15:11:33 UT

What about rounding? Do you round all values after every operation? How do
you do that?
I mean, if there is 10 dollars to be evenly split between three people, one
of them must receive $3.3334, and two others must receive $3.3333 (all
banks I know of work with 1/100 of a cent). Otherwise money will not add

Re: [nodejs] Module naming

a...@equenext.com (Alex Kocharin) — Sat, 25 May 2013 15:03:50 UT

It's an answer to unrelated question. If a package is intended to be used
in public, it should be in public registry (npmjs.org). If it's for
internal use, github will do fine.
But namespaces could do the job if you publish a package with a name like
"stagas.merge". It's quite uncommon though.

Re: [nodejs] Module naming

gsta...@gmail.com (George Stagas) — Sat, 25 May 2013 14:43:02 UT

2013/5/25 Jonathan Ong <jonathanrichard...@gmail.com> :

It seems to work, but then, there's the issue of discoverability. It's
a double edged sword now, either obscure naming and npm indexing or
proper names and invisible.
Why is life so tough.

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

hel...@gmail.com (Matt) — Sat, 25 May 2013 14:39:53 UT

Lua. But then it's a bit of a weird language.

Re: Heroku - Created a facebook app with Node.js which gives type error

stu...@testtrack4.com (Stuart Bentley) — Sat, 25 May 2013 11:22:53 UT

What version of facebook-template-nodejs is your app based on? It should be
in package.json.

Re: [nodejs] Module naming

goktug.kaya...@gmail.com (Göktuğ Kayaalp) — Sat, 25 May 2013 10:06:28 UT

With project-local node_modules directories, this kind of name
collisions should not be an issue.

--
Göktuğ Kayaalp <goktug.kaya...@gmail.com>

Re: [nodejs] Module naming

jonathanrichard...@gmail.com (Jonathan Ong) — Sat, 25 May 2013 09:39:19 UT

just don't bother publishing it. use github namespaces in npm.
{
"dependencies": {
"merge": "stagas/merge"
}

Re: [nodejs] Module naming

a...@kocharin.ru (Alex Kocharin) — Sat, 25 May 2013 08:34:51 UT

RPG name generator could do the job. :)

--
// alex

25.05.2013, 10:49, "George Stagas" <gsta...@gmail.com>:

Re: [nodejs] Re: trying to wrap my head around "promises" - async vs Q

jeanhuguesrob...@gmail.com (Jean Hugues Robert) — Sat, 25 May 2013 08:17:05 UT

Le jeudi 23 mai 2013 19:32:25 UTC+2, Domenic Denicola a écrit :

A different approach:

var read = Parole(); readFile( "dest.txt", "utf8", read );
read.then( function( r ){....} );

Parole() is an "npm l8" subset. See [link]

Is there other ways to improve node.js performance

kettin...@gmail.com (Ket) — Sat, 25 May 2013 08:07:05 UT

I use gzip and child_process api and I see performance increase
dramatically.
However, I feel that performance could be improve further.
Is there any other method do you suggest.
Thank you,

Module naming

gsta...@gmail.com (George Stagas) — Sat, 25 May 2013 06:49:09 UT

Hi all,

I really want to name my modules however I like and be installable and
require-able.

For example, I want to write a 'merge' utility, and I don't want to
struggle coming up with a random set of letters because I want my code
to read require('merge') not require('golalamergifiable').

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

b...@thinkloop.com (Baz) — Sat, 25 May 2013 05:44:23 UT

Thanks a lot Matt and Ravi, very helpful.

Re: [nodejs] Re: Having trouble replicating with npm repo (couchdb) - anyone tried it lately and/or seen this error?

jfuget...@gmail.com (Joshwa Fugett) — Sat, 25 May 2013 05:19:06 UT

It was 1.2 but should work on 1.3 as well since the only major change to
replication in 1.3 from the latest 1.2 was the UUID handling to make
resumes more effective.

daonode: a functional logic solver with built in parser.

simeon.ch...@gmail.com (Simeon Chaos) — Sat, 25 May 2013 03:08:16 UT

I have released daonode on npm and [link]
To use daonode, just:
npm install daonode
Dao is a functional logic solver, unifying code with data, grammar with
program, logic with functional, compiling with running.
Daonode is a porting, rewriting and upgrading from python to coffeecript(so

[ANN] streamcount - Sketch algorithms for real-time analytics

jhurli...@jhurliman.org (John Hurliman) — Sat, 25 May 2013 02:37:54 UT

Hi all,
[link]
I just published the streamcount module to npm. It implements the
HyperLogLog and Count-Min sketch data structures for real-time counting of
unique IDs (useful for unique visitor analytics) or tracking counts of the
top most observed IDs (useful for top viewed pages/videos/products/etc

Re: [nodejs] Re: vnc over gif

andrey.sido...@gmail.com (Andrey) — Sat, 25 May 2013 00:18:44 UT

I added output callback yesterday.
[link]
Actually it could be better interface for node-gif than getGif/setFileName
(have only 'data' callback and wrap the rest of functionality in JS land as
node streams)
I'd like to see vnc-over-gif as one-liner: http.createServer((req,res) ->

Re: [nodejs] Re: vnc over gif

eric.muy...@gmail.com (Eric Muyser) — Sat, 25 May 2013 00:07:28 UT

GIFs have output callbacks? Alright then.. learn something new every day.
Sounds awesome!

Node v0.10.8 (Stable)

i...@izs.me (Isaac Schlueter) — Fri, 24 May 2013 22:46:27 UT

2013.05.24, Version 0.10.8 (Stable)

* v8: update to 3.14.5.9

* uv: upgrade to 0.10.8

* npm: Upgrade to 1.2.23

* http: remove bodyHead from 'upgrade' events (Nathan Zadoks)

* http: Return true on empty writes, not false (isaacs)

* http: save roundtrips, convert buffers to strings (Ben Noordhuis)

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

ravi-li...@g8o.net (// ravi) — Fri, 24 May 2013 22:45:08 UT

There are a lot of performance measurements and benchmarks out there, these days, that pit these languages (and the underlying frameworks) against each other. Given that you wrote (IIRC) that you want to churn through a lot of data, I assume performance is important to you. I haven’t seen any benchmark where Python or other interpreted (or byte-intepreted) languages come in better than JavaScript running on V8. Recently someone posted his measurement of JavaScript parseInt() which fared poorly against a hand-coded version (again in JS), so you may have to profile your code and watch for such quirks if they exist.

Re: [nodejs] Re: Node JS and DOM Manipulation

h...@neosource.cl (Herman Junge) — Fri, 24 May 2013 22:13:01 UT

Last time I used JSDOM it was leaky, So I switched to cheerio. My two cents.

H.-

Re: Node JS and DOM Manipulation

a...@equenext.com (Alex Kocharin) — Fri, 24 May 2013 22:01:50 UT

Jsdom have terrible performance, so think about using "cheerio" instead.
As for cpu-intensiveness, you have plenty of options here. Easiest solution
would be to increase an amount of node.js processes using "cluster"
library. But the best way is to write another node.js server that would do
all blocking tasks, so your frontend would be a bridge between that server

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

hel...@gmail.com (Matt) — Fri, 24 May 2013 22:01:05 UT

I think Java is well proven to be faster at this point. But it's a lot more
complicated writing Java code.

A typical example is if you started filling an object up with millions of
keys. The garbage collector is going to have a bar hair day if you do that.

I don't find that to be entirely true. Though it really comes down to a

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

b...@thinkloop.com (Baz) — Fri, 24 May 2013 21:23:05 UT

Thanks for the responses gents. As a little background, the reason I'm
considering node for this is because the datastore in question is Firebase
- a real-time document store with a node sdk. It has a REST api too, so I
don't *have* to use node, but it'd be nice to plug in to the real-time
features.

Re: [nodejs] Re: vnc over gif

christ...@tellnes.no (Christian Tellnes) — Fri, 24 May 2013 21:08:32 UT

2013/5/24 mscdex <msc...@gmail.com>:

Time to downgrade node.

--
Sincerely, Christian Vaagland Tellnes
Phone: +4791861617
[link]

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

hel...@gmail.com (Matt) — Fri, 24 May 2013 20:30:04 UT

My point was simply that saying that floating point numbers are "as precise
as integers up to 50 bits" is incorrect and misleading. Pocket change money
values can result in incorrect calculations if using floating point.

No I'm not the OP - I never claimed that. Doing it as integers/pennies is

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

m...@hahnca.com (Mark Hahn) — Fri, 24 May 2013 20:14:13 UT

It gives the correct answer after rounding. Also, integers certainly can't
do that. What is your point?

point anyway.

Right. The floating point in js provides integer support. For money use
floating point as integers.

You can do anything in js you can do with integers up to 50 bits of

Re: [nodejs] HTTP - how to send multiple pre-cached gzipped chunks?

hel...@gmail.com (Matt) — Fri, 24 May 2013 20:08:35 UT

In *theory* you might be able to do this by sending two multipart/mixed
MIME sections, each having a Content-Encoding: gzip header. But I can't
imagine that any browser would support it and display it properly.

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

hel...@gmail.com (Matt) — Fri, 24 May 2013 19:50:16 UT

It's not a myth at all if you're actually using floating point numbers
though. Try this in node: 1.03 - 0.42.

If you're keeping the units in pennies then you're not using floating point
anyway.

Matt.

Re: [nodejs] HTTP - how to send multiple pre-cached gzipped chunks?

t...@creationix.com (Tim Caswell) — Fri, 24 May 2013 19:45:13 UT

I'm afraid I don't know gzip format well enough to answer that. It's
fairly well documented at [link] though.

Re: [nodejs] HTTP - how to send multiple pre-cached gzipped chunks?

jane...@gmail.com (Sławek Janecki) — Fri, 24 May 2013 19:42:40 UT

Is there any way to 'hack' it? For example striping gzpi headers from 2nd
gzip chunk? Or that header is binded to gziped data?

Re: [nodejs] HTTP - how to send multiple pre-cached gzipped chunks?

t...@creationix.com (Tim Caswell) — Fri, 24 May 2013 19:37:28 UT

gzip has internal headers that must only appear at the beginning. You
can't send two gzip documents in the same document. The browsers don't
support that.

If you have the same two chunks all the time, you can combine and then gzip
once and send the one resulting chunk.

Re: [nodejs] Re: Synchronous code with node.js for utility scripts

mikeal.rog...@gmail.com (Mikeal Rogers) — Fri, 24 May 2013 19:05:18 UT

I would put it like this:

People are writing concurrent applications. Basically, people who used to write Rails apps are writing servers now. This is harder.

The hardest part of concurrent programming is understand and managing state mutations. We all hate dealing with threads in C right?

There are many different ideas on this list about what the best visual representation of state mutations is. JavaScript is not Erlang, it doesn't enforce a serialization between two pieces of code that will run concurrently so that they don't mutate shared state, JavaScript runs exactly one piece of code at any time and *we* write APIs that give the programmer an indication of *when* that state is allowed to change and assume it will not change the rest of the time.

HTTP - how to send multiple pre-cached gzipped chunks?

jane...@gmail.com (Sławek Janecki) — Fri, 24 May 2013 19:04:20 UT

Lets say I have 2 individually gziped html chunks in memory. Can I send
chunk1+chunk2 to HTTP client? Does any browser supports this? Or there is
no way to do this and I have to gzip the whole stream not individual chunks?
I want to serve to clients for example chunk1+chunk2 and chunk2+chunk1 etc

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

m...@hahnca.com (Mark Hahn) — Fri, 24 May 2013 18:41:49 UT

monetary transactions.

This is somewhat of a myth. People are afraid of floating point numbers
because they are somehow "imprecise". In fact, up to around 50 bits they
are as precise as integers. I've used them for money many times. It is as
simple as keeping the units in pennies.

Re: [nodejs] Re: Synchronous code with node.js for utility scripts

freshene...@gmail.com (Billy Te) — Fri, 24 May 2013 18:41:53 UT

@Raynos and Bruno Jouhier
Creating a good language and good supporting functionality is not about
catering to what *you* like or what *you* are ok with dealing with. Its
about creating easy to use, powerful functionality that can be combined in
ways that
A. make new ways of doing things possible, so people can experiment and

Re: [nodejs] Re: Announcing StrongLoop Node 1.0 GA, an enterprise-ready distro of Node.js.

s...@strongloop.com (Sam Roberts) — Fri, 24 May 2013 17:02:39 UT

On Fri, May 24, 2013 at 9:39 AM, Matteo Collina

We're sorry about that, the links are missing from the package
metadata, we'll fix that, but you can find the repos here:

[link]

Cheers,
Sam

Re: [nodejs] Re: vnc over gif

hel...@gmail.com (Matt) — Fri, 24 May 2013 16:45:30 UT

Would that be screenshotception?

Re: [nodejs] Re: Announcing StrongLoop Node 1.0 GA, an enterprise-ready distro of Node.js.

matteo.coll...@gmail.com (Matteo Collina) — Fri, 24 May 2013 16:39:36 UT

Hi Jimmy,

All these packages have no links to github :).

Cheers,

Matteo

2013/5/22 Jimmy Guerrero <ji...@strongloop.com>

Re: [nodejs] Re: vnc over gif

nat...@tootallnate.net (Nathan Rajlich) — Fri, 24 May 2013 16:27:46 UT

Sounds cool! Any screenshots?

Re: [nodejs] Re: Having trouble replicating with npm repo (couchdb) - anyone tried it lately and/or seen this error?

virtuala...@gmail.com (andy e) — Fri, 24 May 2013 14:56:03 UT

Joshwa,

Cool, thanks for the tip. Were you running Couch 1.2 or 1.3?

We still need to try a few of these suggestions (guy doing most of this has
been out for a week) but will definitely give this a shot.

Thanks!

Andy

Re: vnc over gif

msc...@gmail.com (mscdex) — Fri, 24 May 2013 11:49:45 UT

Time to upgrade my browser :-(

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

i...@bnoordhuis.nl (Ben Noordhuis) — Fri, 24 May 2013 11:24:50 UT

It's certainly possible but it's not node's primary strength.

It depends on what your business logic consists of. For example,
numbers in JS are 64 bits doubles so you're dealing with inexact
floating-point arithmetic all the time. Which is okay for most use
cases but not, say, when you are processing monetary transactions.

[ANN] vnc over gif

andrey.sido...@gmail.com (Andrey) — Fri, 24 May 2013 10:09:50 UT

[link]
Friday evening project: vnc viewer based on animated gif image stream.
Browser requirement: netscape 2.0+
Regards
Andrey.

Re: [nodejs] Non-web always-blocking cpu-intensive high-memory node worker

pedro.teixe...@gmail.com (Pedro Teixeira) — Fri, 24 May 2013 08:54:17 UT

Node is great for doing I/O and not much else, so I'd settle on using node as master and have child processes, defining a clear interface between the 2 (perhaps JSONStream?) and then use whatever technology is more appropriate for implementing these child processes, which is where the CPU-heavy tasks get done.