The community has created a lot of rad logos you can find here: http://tableflip.io:1234/
Node.js, a popular tool for building modern internet services, has split in two
151–160 of 166 posts
Re: Node.js, a popular tool for building modern internet services, has split in two
#152Earlier quoted context omitted.
You may be speaking of a particular implementation or engine. JS, the language, has no such concept of a "thread". The standard describes execution of a valid program as linear. Libraries may add functions such as event listeners or threading or sockets, but these are not part of the language. And yes, to be pedantic, by JS I'm refering to ECMAScript, or ECMA-262. If by JS you mean JavaScript the implementation by Mo…
Timers are sort of threads..
Let me know if you disagree... Don't just hide behind a down vote...
Re: Node.js, a popular tool for building modern internet services, has split in two
#153Re: Node.js, a popular tool for building modern internet services, has split in two
#154There is a big advantage to node.js that used to be mentioned a lot in its early days, but not much now. The advantage is still there, but it's only noticeable if a developer has experience in other server languages. The big advantage is that node.js had an asynchronous development model from the beginning. This caused all the code written since then to also be written using async. When a node.js project imports othe…
Great comment - I do think the whole 'async by default' is a huge benefit, but I would add an asterisk and say you can technically write a module that performs synchronous I/O if you wanted to (see, for example, synchronous filesystem calls). So there's a possibility some random synchronous code blocking could happen with an untrusted module, albeit very unlikely. As far as I know the fs.*FileSync calls are the only ones.
Re: Node.js, a popular tool for building modern internet services, has split in two
#155Earlier quoted context omitted.
It isn't that. Really it's Fedor and Mikeal pushing it a lot, not the strongloop guys. The other core devs are behind it, too, except a couple from Joyent. It really has nothing to do with corporate power struggles (that's more what Joyent's advisory board is about, frankly)... it has to do with developers getting really frustrated at the stalled pace of development on the Joyent branch. The real objective is to get…
New features for numerical computing? I am intrigued... for me that essentially means operator overloading, including []. I think that would open the door for implementing a numpy like module for Node. Is that the plan?
No, operator overloading isn't in the language spec, with reason. I think numerical computing libs like LAPACK, if ported to JS, will probably require a wrapper around 64-bit floats (a la BigDecimal) and math operators that are really function calls. The plan has been to look into transpiling from fortran to asm.js although my personal feeling is it would be better just to use the C API and compile a module that statically links in the necessary libs. They'll figure it out...
Re: Node.js, a popular tool for building modern internet services, has split in two
#156I wish this would have come before. TJ and others may not have quit then. I also feel that the community has been dwindling for some time and node v1.0 is taking forever. I look forward to io.js. This could be something that is required to restore faith - something of the devs, by the devs and for the devs.
Re: Node.js, a popular tool for building modern internet services, has split in two
#157Earlier quoted context omitted.
While I think abandoning threading was originally a good move because it spawned (no pun intended) new methods of chaining callbacks together, I'm concerned that there is really no way out of callback hell by way of callbacks. So I'm wondering if Node.js, Io.js or both will embrace coroutines, yield and generators. The real danger of threads was always shared memory, not so much simultaneous execution. I'm hoping tha…
If you want to get out of callback hell, I Promise you'll enjoy this library called Bluebird.
`Bluebird` looks good, i gonna try it out. thanks.
Re: Node.js, a popular tool for building modern internet services, has split in two
#158Earlier quoted context omitted.
> one-word non-functional changes What about typos in docs? Contextually it seems reasonable to accept changes of a single word which may cause confusion on operational grounds. Is a gendered word really different? Operationally, it would appear differentiating between pronouns might be required in documentation if some readers of the docs are offended by the masculine use. One could certainly argue that with excessi…
> What about typos in docs? In my opinion these trivial changes should be submitted as text in a bug report rather than patches or pull requests. For brevity a regex statement like s/foo/baz/ can be used.
That's a way one could do things, and fairly common with non-GitHub repositories. But it's not the cultural norm on GitHub. The typical process is to submit pull requests even for small doc changes. The interface encourages this by even having an "edit" button and online editor, which wraps up the fork/commit/pull-request cycle into a button push. And the GitHub docs encourage that as well.
Re: Node.js, a popular tool for building modern internet services, has split in two
#159Earlier quoted context omitted.
> What about typos in docs? In my opinion these trivial changes should be submitted as text in a bug report rather than patches or pull requests. For brevity a regex statement like s/foo/baz/ can be used.
That's a way one could do things, and fairly common with non-GitHub repositories. But it's not the cultural norm on GitHub. The typical process is to submit pull requests even for small doc changes. The interface encourages this by even having an "edit" button and online editor, which wraps up the fork/commit/pull-request cycle into a button push. And the GitHub docs encourage that as well.
I think any serious projects should have a CLA, or require sign off like the Linux project does, and suggesting a change is the only way to get around having to deal with that.
For known contributors, yeah, it's a nice feature.
Re: Node.js, a popular tool for building modern internet services, has split in two
#160Earlier quoted context omitted.
That's a way one could do things, and fairly common with non-GitHub repositories. But it's not the cultural norm on GitHub. The typical process is to submit pull requests even for small doc changes. The interface encourages this by even having an "edit" button and online editor, which wraps up the fork/commit/pull-request cycle into a button push. And the GitHub docs encourage that as well.
I think any serious projects should have a CLA, or require sign off like the Linux project does, and suggesting a change is the only way to get around having to deal with that. For known contributors, yeah, it's a nice feature.
CLA?