Streams for example aren't part of v8.

On Sunday, 20 July 2014 06:19:49 UTC+4, Phoscur wrote:
>
>  Aren't we just speeding on the work of the V8 team? NodeJS just leverages 
> a low level API to that beast (and that's why there are callbacks, they are 
> low level function blocks in javascript.
> So it's not about performance and Callbacks..
>
> Where exactly are the usability leaks?
>
> TJ thank you for your great frameworks like express, socket.io & co!
>
> Ph
>
> Am 07.07.2014 06:28, schrieb tjholowaychuk:
>  
> Weird apparently what I posted didn't work. Anyway I think it's a very odd 
> choice for a JavaScript platform to strive for performance over usability, 
> usability is the *only* reason you would ever go with JavaScript, because 
> people know it. It's a terrible choice of a language if you're shooting for 
> raw performance, and even worse is that you really shouldn't scale your 
> application based on raw performance. If you have to serve tons of requests 
> then you also have the money to spawn an machine or two, look at YouTube 
> even it uses Python and it's much larger than anything node has been used 
> for, it's really just not a concern these days. Startups should be 
> concerned with robustness, not raw performance that they don't even need.
>
> On Sunday, 6 July 2014 20:04:43 UTC-7, Chaoran Yang wrote: 
>>
>> I think what TJ complained about Nodejs are valid points. However I also 
>> think Nodejs preference of performance over usability is not wrong. We need 
>> to understand the Nodejs is not the best choice for all web applications, 
>> just like C is not the best choice for programs. There are already loads of 
>> languages that favors usability, and Nodejs should not become one of them. 
>> Nodejs exists because it is different. It provides an alternative for those 
>> who cares about performance, and doesn't bother to get their hands dirty in 
>> low level details. 
>>
>>  I do agree with TJ with the fact that Streams are broken in Nodejs is 
>> becoming a problem. It should be a major help for simplifying asynchronous 
>> programming but it is still in unstable state now.
>>
>>  Chaoran
>>
>> On Friday, July 4, 2014 10:40:25 AM UTC-5, [email protected] wrote: 
>>>
>>> TJ is leaving node as he posted here 
>>> https://medium.com/code-adventures/4ba9e7f3e52b  
>>>
>>>  What do you think about it and what projects are you using that came 
>>> from him?
>>>  
>>   -- 
> Job board: http://jobs.nodejs.org/
> New group rules: 
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules: 
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> --- 
> You received this message because you are subscribed to the Google Groups 
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To post to this group, send email to [email protected] <javascript:>
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/nodejs/8bfb84c3-60ae-4848-8fce-deae4f6367d8%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/nodejs/8bfb84c3-60ae-4848-8fce-deae4f6367d8%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>  

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/228e5b61-2c35-490e-afff-bb8e5b32a474%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to