This guy Ted doesn't deserve all this attention. His angry blog post is just that... An angry blog post. He clearly cares very little about us devs (or the Node.js community). he is screaming for attention... Calling names on people he hasn't even met (coward/bully) and belittling tech he doesn't even understand (troll - silly programming example). I decided to respond when I saw that he is actually 'silently' reading this thread... (coward) and not really responding w/ the same enthusiasm. Sad to see fellow devs being so negative and nasty. Anyway... back to coding!
Sent from my iPhone
On Oct 2, 2011, at 7:48 PM, Joshua Kehn <josh.k...@gmail.com> wrote:
>> On Sun, Oct 2, 2011 at 19:34, Joshua Kehn <josh.k...@gmail.com> wrote: >>> Looks like you wouldn't use PHP either:
>>> Joshs-MacBook-Pro:~ josh$ time curl http://localhost:1337/ >>> 165580141 >>> real 0m3.942s >>> user 0m0.004s >>> sys 0m0.004s >>> Joshs-MacBook-Pro:~ josh$ time curl http://localhost:8888/fibserver.php >>> Number is: 165580141 >>> real 1m22.709s >>> user 0m0.004s >>> sys 0m0.005s
> This guy Ted doesn't deserve all this attention. His angry blog post is just that... An angry blog post. He clearly cares very little about us devs (or the Node.js community). he is screaming for attention... Calling names on people he hasn't even met (coward/bully) and belittling tech he doesn't even understand (troll - silly programming example). I decided to respond when I saw that he is actually 'silently' reading this thread... (coward) and not really responding w/ the same enthusiasm. Sad to see fellow devs being so negative and nasty. Anyway... back to coding!
> Sent from my iPhone
> On Oct 2, 2011, at 7:48 PM, Joshua Kehn <josh.k...@gmail.com> wrote:
>> Ted's (tjdzi...@gmail.com) and mine are shared on our respective blogs as well.
>> Now getting Ted to respond to comments is an entirely different matter. My experience is he won't.
>>> On Sun, Oct 2, 2011 at 19:34, Joshua Kehn <josh.k...@gmail.com> wrote: >>>> Looks like you wouldn't use PHP either:
>>>> Joshs-MacBook-Pro:~ josh$ time curl http://localhost:1337/ >>>> 165580141 >>>> real 0m3.942s >>>> user 0m0.004s >>>> sys 0m0.004s >>>> Joshs-MacBook-Pro:~ josh$ time curl http://localhost:8888/fibserver.php >>>> Number is: 165580141 >>>> real 1m22.709s >>>> user 0m0.004s >>>> sys 0m0.005s
> > This guy Ted doesn't deserve all this attention. His angry blog post is just that... An angry blog post. He clearly cares very little about us devs (or the Node.js community). he is screaming for attention... Calling names on people he hasn't even met (coward/bully) and belittling tech he doesn't even understand (troll - silly programming example). I decided to respond when I saw that he is actually 'silently' reading this thread... (coward) and not really responding w/ the same enthusiasm. Sad to see fellow devs being so negative and nasty. Anyway... back to coding!
> > Sent from my iPhone
> > On Oct 2, 2011, at 7:48 PM, Joshua Kehn <josh.k...@gmail.com> wrote:
> >> Ted's (tjdzi...@gmail.com) and mine are shared on our respective blogs as well.
> >> Now getting Ted to respond to comments is an entirely different matter. My experience is he won't.
>>> This guy Ted doesn't deserve all this attention. His angry blog post is just that... An angry blog post. He clearly cares very little about us devs (or the Node.js community). he is screaming for attention... Calling names on people he hasn't even met (coward/bully) and belittling tech he doesn't even understand (troll - silly programming example). I decided to respond when I saw that he is actually 'silently' reading this thread... (coward) and not really responding w/ the same enthusiasm. Sad to see fellow devs being so negative and nasty. Anyway... back to coding!
>>> Sent from my iPhone
>>> On Oct 2, 2011, at 7:48 PM, Joshua Kehn <josh.k...@gmail.com> wrote:
>>>> Ted's (tjdzi...@gmail.com) and mine are shared on our respective blogs as well.
>>>> Now getting Ted to respond to comments is an entirely different matter. My experience is he won't.
>>>>> On Sun, Oct 2, 2011 at 19:34, Joshua Kehn <josh.k...@gmail.com> wrote: >>>>>> Looks like you wouldn't use PHP either:
>>>>>> Joshs-MacBook-Pro:~ josh$ time curlhttp://localhost:1337/ >>>>>> 165580141 >>>>>> real 0m3.942s >>>>>> user 0m0.004s >>>>>> sys 0m0.004s >>>>>> Joshs-MacBook-Pro:~ josh$ time curlhttp://localhost:8888/fibserver.php >>>>>> Number is: 165580141 >>>>>> real 1m22.709s >>>>>> user 0m0.004s >>>>>> sys 0m0.005s
As an aside, this assumes CPU pipelining does not occur for the single threaded Node and that threads are each given one core (woot in Java7 for getting that done right, I for one look forward to sane multi-core threads). Threads do not scale on cores as people might think they do.
If people don't want to try new things, that's their problem and
that's fine. But what's the point of insulting those who do and who
are making things move forwards (even if not always in a straight
line).
Bruno
On Oct 2, 11:42 pm, Tauren Mills <tau...@groovee.com> wrote:
For someone who's only worked professionally for a few years (according to linkedin) it seems a bit early to be yelling "Get off my lawn" like that, but there you have it. :-)
Have you *really* made the test for ruby ? I tried with PHP, python and scala, and node was actually the fastest (I mean, really, like 8 seconds versus 2 minutes). I wasn't even expecting that, but I must thank Ted for this: I would have never made such a test without his motivation, and now I can really tell Node is damn fast, thanks v8, and thanks Ted. Le 3 oct. 2011 00:51, "Jorge" <jo...@jorgechamorro.com> a écrit :
Now we're just looking at the optimizations done by each compiler / interpreter. V8 and the JVM are doing work to optimize the recursive calls which places them ahead of languages generally regarded as “faster“.
> Have you *really* made the test for ruby ? I tried with PHP, python and scala, and node was actually the fastest (I mean, really, like 8 seconds versus 2 minutes). I wasn't even expecting that, but I must thank Ted for this: I would have never made such a test without his motivation, and now I can really tell Node is damn fast, thanks v8, and thanks Ted.
> Le 3 oct. 2011 00:51, "Jorge" <jo...@jorgechamorro.com> a écrit : > On 02/10/2011, at 23:42, Tauren Mills wrote:
Thanks everyone for voicing your reaction to that article. I regret bringing it up and wasting everyone's time with this troll, but I'm sure it would have came up regardless. Everyone get back to work!
>> On Oct 2, 2011, at 14:42, Tauren Mills wrote:
> For someone who's only worked professionally for a few years (according to linkedin) it seems a bit early to be yelling "Get off my lawn" like that, but there you have it. :-) > -- > Ask Bjørn Hansen, http://askask.com/
Bjørn, I'm assuming your comment is a misplaced response to Isaac in the 'metaprogramming' thread, where he says "Maybe this is the part where I shake my cane at the ruby kids on my lawn". I have far more than a "few professional years" behind me, but I have yet to start yelling "get off my lawn". At least give me another decade... ;)
>> For someone who's only worked professionally for a few years (according to linkedin) it seems a bit early to be yelling "Get off my lawn" like that, but there you have it. :-)
> I'm assuming your comment is a misplaced response to Isaac in > the 'metaprogramming' thread,
I'm really sorry. My comment was, I thought obviously, directed at Ted's "article" -- not at you or Isaac! I wouldn't have replied publicly further in this thread, but I just wanted to make that clear.
> where he says "Maybe this is the part where I shake my cane at the ruby kids on my > lawn". I have far more than a "few professional years" behind me, but > I have yet to start yelling "get off my lawn". At least give me > another decade... ;)
We're probably all there now and then without realizing it. ;-)
Says who? I do trading algo in node.js and some computational tasks last for hours on a cluster. And it's perfectly fine with me! :) Web-server? Who said web-server? :)
Note that this header is in his whole website, not only this page. Which means the whole guy is a troll, and that we all already knew :) But still, many small-brained people (which includes many ITs "leaders" and managers) could believe his bullshit :(
@Egor, I doubt you're the only one! Presumably you have some mechanism
to pool Node processes and queue jobs when the pool is busy?
In the rush to defend Node and bash the troll, most overlook the valid
point that cpu-intensive tasks should be performed asynchronously, and
child_process.fork() is not a complete solution.
On Oct 3, 1:53 am, Egor Egorov <egor.ego...@gmail.com> wrote:
> Says who? I do trading algo in node.js and some computational tasks last for
> hours on a cluster. And it's perfectly fine with me! :) Web-server? Who said
> web-server? :)
> On Monday, October 3, 2011 1:25:34 AM UTC+3, Isaac Schlueter wrote:
> > Seriously, who here *hasn't* heard that you shouldn't do cpu-intensive
> > operations in JavaScript?
On Mon, Oct 3, 2011 at 3:48 AM, Liam <networkimp...@gmail.com> wrote: > @Egor, I doubt you're the only one! Presumably you have some mechanism > to pool Node processes and queue jobs when the pool is busy?
> In the rush to defend Node and bash the troll, most overlook the valid > point that cpu-intensive tasks should be performed asynchronously, and > child_process.fork() is not a complete solution.
> On Oct 3, 1:53 am, Egor Egorov <egor.ego...@gmail.com> wrote: > > Says who? I do trading algo in node.js and some computational tasks last > for > > hours on a cluster. And it's perfectly fine with me! :) Web-server? Who > said > > web-server? :)
> > On Monday, October 3, 2011 1:25:34 AM UTC+3, Isaac Schlueter wrote:
> > > Seriously, who here *hasn't* heard that you shouldn't do cpu-intensive > > > operations in JavaScript?
No, but with a thread per connection, with n cores you'd have n threads running in parallel.
> I tried with PHP, python and scala, and node was actually the fastest (I mean, really, like 8 seconds versus 2 minutes). I wasn't even expecting that, but I must thank Ted for this: I would have never made such a test without his motivation, and now I can really tell Node is damn fast, thanks v8, and thanks Ted.
Ruby is also (notably) slower than v8/JS. It will win the race though, but only because of the multiple threads of execution (in a multicore machine). -- Jorge.
> If people don't want to try new things, that's their problem and > that's fine. But what's the point of insulting those who do and who > are making things move forwards (even if not always in a straight > line).
> In the rush to defend Node and bash the troll, most overlook the valid > point that cpu-intensive tasks should be performed asynchronously, and > child_process.fork() is not a complete solution.
