3 ms·
At least from what I've seen publicly on v8-users list, that is not true. Google has not, and seemingly, will not pick a side. Or, if you must, they've picke
by oso2k 12y ago
At least from what I've seen publicly on v8-users list, that is not true. Google has not, and seemingly, will not pick a side. Or, if you must, they've picked Chrome/Chromium and its 6-week version/development cycle. The v8 team has always been clear on this. Their primary (only?) customer for v8 is Chrome.
- domenicd 12y agoHi, can you point to where on v8-users you got this impression? In general we are much happier with how io.js aligns with supported V8 versions.
- oso2k 12y agoHere's an example [0] where Googles showed they preferred their ICU implementation over system, in effect, remaining self-sufficient & neutral of the embedder's concern. And as an independent embedder with a non-public project (as of yet), I prefer that neutrality. For other embedders, however, like TeaJS, SilkJS, v8-juice/cvv8, narwahlJS, this was probably their undoing, at least in my opinion. Stephen Beal considered it lack of documentation & support [1]. I have seen a concerted effort over the past 12 months to improve that. [0] https://groups.google.com/forum/#!searchin/v8-users/support/v8-users/eGbh2eG9OOI/OWO5eCFJBy0J https://groups.google.com/forum/#!searchin/v8-users/support/... [1] https://groups.google.com/d/msg/v8-users/MUq5WrC2kcE/Z3LyOmELzD0J https://groups.google.com/d/msg/v8-users/MUq5WrC2kcE/Z3LyOmE...
- inglor 12y agoThe other reply you got is from someone working for Google on this by the way.