31–40 of 75 posts
It's scary what you can do with machine translation these days...
Funny how it changed: for (int i = 0; v8::V8::IdleNotification() && i to: for (int i = 0; v8:: V8:: IdleNotification () & & i
Edit: By 'code tags' i mean literal tags.
These only sound like problems if you need to keep it single process. If you break out the javascript interpreter via fastcgi workers just like people do with php on nginx it becomes mostly moot points right? At that point its limited to 500 req/sec/core, but frankly these days that means 4000 req/s, which, hell, I'll take it. Granted thats assuming you can actually run a fastcgi/v8 setup, I've never looked. I wonder…
Earlier quoted context omitted.
Funny how it changed: for (int i = 0; v8::V8::IdleNotification() && i to: for (int i = 0; v8:: V8:: IdleNotification () & & i
He probably should've wrapped this bit in code tags. Edit: By 'code tags' i mean literal tags.
tag.
It's scary what you can do with machine translation these days...
Does someone want to change the title to be clearer?
While 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…
It's scary what you can do with machine translation these days...
I thought exactly the same thing! I still remember being able to play a game with one of my friends where we'd translate a sentence to German then back to English and laugh at how mangled it was…
Seems like process isolation a la fastcgi is the practical way to go, unless the V8 team itself wants V8 to be embeddable in a "reliable" way (meaning, it recovers from its own errors without corrupting the process it's embedded in).
A 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?