It's scary what you can do with machine translation these days...
Seriously.. I didn't even realize that was a translation till I finished the first paragraph.
that or we have bad grammar sentences, sometimes.
The author of Nginx on why V8 is not suitable for web servers
11–20 of 75 posts
Re: The author of Nginx on why V8 is not suitable for web servers
#12While an interesting article in its own right, it has nothing to do with node.js, except that this happens to be a criticism of the way V8 works, which node.js is built on. However, they may not be using things in the same way he is, or there could be mitigating circumstances which make it possible for node.js to pull this off. (I don't know anything about node.js internals, I just know this article isn't about it, a…
I disagree. Where V8 can run is a core part of the deployment surface of node.js, so what server authors think about V8 and it's suitability for integration and deployment very much matter to node.js.
Remember, 'does rails scale'? :|
Re: The author of Nginx on why V8 is not suitable for web servers
#13It's scary what you can do with machine translation these days...
Haha, I thought your reply was talking about how the V8 engine worked(translating to machine specific code), instead of the language translator used on the blog post.
Re: The author of Nginx on why V8 is not suitable for web servers
#14It's scary what you can do with machine translation these days...
Not only is the translation of a surprisingly high quality, but reading the original in Russian is more awkward since a lot of the technical terms are originally English. I needed to read a particular portion 3 times before I realized it meant memory allocation.
I though the same thing. I learned all the tech terms in English, so when I read "sborka musora" instead of "garbage collection" it somehow makes me smile.
Re: The author of Nginx on why V8 is not suitable for web servers
#15While an interesting article in its own right, it has nothing to do with node.js, except that this happens to be a criticism of the way V8 works, which node.js is built on. However, they may not be using things in the same way he is, or there could be mitigating circumstances which make it possible for node.js to pull this off. (I don't know anything about node.js internals, I just know this article isn't about it, a…
I disagree. Where V8 can run is a core part of the deployment surface of node.js, so what server authors think about V8 and it's suitability for integration and deployment very much matter to node.js. Remember, 'does rails scale'? :|
Even if every one of these issues applies to node.js, this article is not "on node.js". The title is incorrect, no matter what.
Re: The author of Nginx on why V8 is not suitable for web servers
#16The state of todays base of node (v8) has nothing to do with the concept/paradigm its trying to put forward -- that is event driven web apps. Hence, one must not discard node as a bad solution only because v8 is not optimal in all situations.
Everything is always a work in progress.
Re: The author of Nginx on why V8 is not suitable for web servers
#17It's scary what you can do with machine translation these days...
Funny how it changed:
for (int i = 0; v8::V8::IdleNotification() && i for (int i = 0; v8:: V8:: IdleNotification () & & i Re: The author of Nginx on why V8 is not suitable for web servers
#18It's scary what you can do with machine translation these days...
It likely was not completely translated by machine. Google Translate lets anyone reading the translation edit it to fix errors. Highlight some text and notice the link that appears allowing you to "Contribute a better translation" for that particular passage.
Re: The author of Nginx on why V8 is not suitable for web servers
#19A thought: why not have node developers fork V8, and modify that to make it ready for server deployment? Has the coreteam and/or Dahl thought about this?
Re: The author of Nginx on why V8 is not suitable for web servers
#20It's scary what you can do with machine translation these days...
It likely was not completely translated by machine. Google Translate lets anyone reading the translation edit it to fix errors. Highlight some text and notice the link that appears allowing you to "Contribute a better translation" for that particular passage.
It's more likely that it only helps train Google Translate, and doesn't actually apply any changes directly to the translated text. Otherwise vandalism would be way too easy.