3 ms·

Doing a first version of almost anything I've tried in Node is usually much faster than alternative platforms. Do you say this because of the libraries availab

Doing a first version of almost anything I've tried in Node is usually much faster than alternative platforms. Do you say this because of the libraries available for it? (curious, wanting to jump to node).

tracker1 10y ago
I mean faster to get up and running... development time that is. Mostly, for me, because I'm doing front end work in JS, using mostly the same tooling npm, babel (though with webpack on front end now). It's just so much faster to get going if you're developing the full stack, and already in JS heavy land anyway. Not having to context switch for the backend is huge... being able to use a document/object/json database isn't as big of a boost but still nice. On the db side, I've been using the template wrappers so that I can write a simple query and it turns it into a parameterized query returning a promise. async function getRecords(baz) { return await sql.query` SELECT a, b FROM foo WHERE foo.bar = ${baz} `; } So, I still have to think about some SQL, but still usually better than trying to twist ORMs into shape. Overall, for the past 6 years or so (since 0.8) I've been using Node pretty heavily (moving from more C# on the backend) and really haven't missed it at all. Even though the core .net and more open-source stuff has been interesting... Managed to dockerize a few trivial .Net apps using the dotnet onbuild base containers. If you're using windows, the only gotchas are you need a C++ build environment (Visual C++ 2015 Build Tools, checking all options) and Python 2.7.x in order to build any binary modules... most of which now run without issue on windows, was a much bigger problem in 0.8-0.10 ...
FullMtlAlcoholc 10y ago
Although the parent didn't allude to it in his reply, the network effects that the npmjs registry provides is huge and is its killer feature. In my experience, there's usually multiple, specific modules for anything you're trying to do. Case in point, I'm developing a music curation service and there are no less than 5 recently updated modules for downloading from youtube and scores of them for converting playlists from one service to another.

tracker1 10y ago

I mean faster to get up and running... development time that is. Mostly, for me, because I'm doing front end work in JS, using mostly the same tooling npm, babel (though with webpack on front end now). It's just so much faster to get going if you're developing the full stack, and already in JS heavy land anyway. Not having to context switch for the backend is huge... being able to use a document/object/json database isn't as big of a boost but still nice. On the db side, I've been using the template wrappers so that I can write a simple query and it turns it into a parameterized query returning a promise. async function getRecords(baz) { return await sql.query` SELECT a, b FROM foo WHERE foo.bar = ${baz} `; } So, I still have to think about some SQL, but still usually better than trying to twist ORMs into shape. Overall, for the past 6 years or so (since 0.8) I've been using Node pretty heavily (moving from more C# on the backend) and really haven't missed it at all. Even though the core .net and more open-source stuff has been interesting... Managed to dockerize a few trivial .Net apps using the dotnet onbuild base containers. If you're using windows, the only gotchas are you need a C++ build environment (Visual C++ 2015 Build Tools, checking all options) and Python 2.7.x in order to build any binary modules... most of which now run without issue on windows, was a much bigger problem in 0.8-0.10 ...

FullMtlAlcoholc 10y ago

Although the parent didn't allude to it in his reply, the network effects that the npmjs registry provides is huge and is its killer feature. In my experience, there's usually multiple, specific modules for anything you're trying to do. Case in point, I'm developing a music curation service and there are no less than 5 recently updated modules for downloading from youtube and scores of them for converting playlists from one service to another.