It'd be nice if there was a ./configure flag to set V8 options by default. The problem so far has been that many of the newer experimental behind-a-flag features in V8 have traditionally been unstable or performance-destroying, so we're a little bit timid about setting them by default. We've discussed making Node follow Chrome's defaults instead of V8's. I would be -1 on setting flags that *aren't* enabled by default in chrome.
Maybe send a pull request and we can have the discussion there, where it can be more productive than Ye Olde Mailinge Liste. In the short term, your module can test for whatever it needs and throw early with a helpful message. If it's a binary script, you can set the shebang to `#!/usr/bin/env node --harmony_whatevers` and it'll Just Work on unix, and npm will DTRT on Windows when it writes the .bat shim. (Probably not telling you anything you don't already know.) On Fri, Jan 18, 2013 at 12:01 PM, Mikeal Rogers <[email protected]> wrote: > I can't speak for everyone, but this is my concern. > > The node project has opted out of a *huge* amount of endless debate by not > defining either the language or the vm and having a policy of offloading > that decision to v8, etc. > > For me this isn't about being against enabling any particular feature but > about using "default" or "vanilla" v8. This policy has gotten a little more > complex as it seems Chrome is enabling features in v8 that are actually not > included by default. > > I don't think we'll get very far arguing for or against enabling specific > features in v8 but I do think it's worth having a conversation about > compiling with whatever latest stable Chrome enables rather than the v8 > default if v8 continues to not enable features by default that are done and > stable. > > -Mikeal > > On Jan 18, 2013, at January 18, 201311:56 AM, Mark Hahn <[email protected]> > wrote: > > I'm curious about something. What would be the disadvantage to enabling > harmony by default in node? > > I and at least one other have a problem in that we have a module which > requires harmony and there is no way to enable it from npm. > > > > On Fri, Jan 18, 2013 at 11:51 AM, Isaac Schlueter <[email protected]> wrote: >> >> 2013.01.18, Version 0.9.7 (Unstable) >> >> * V8: Upgrade to 3.15.11.7 >> >> * npm: Upgrade to 1.2.2 >> >> * punycode: Upgrade to 1.2.0 (Mathias Bynens) >> >> * repl: make built-in modules available by default (Felix Böhm) >> >> * windows: add support for '_Total' perf counters (Scott Blomquist) >> >> * cluster: make --prof work for workers (Ben Noordhuis) >> >> * child_process: do not keep list of sent sockets (Fedor Indutny) >> >> * tls: Follow RFC6125 more strictly (Fedor Indutny) >> >> * buffer: floating point read/write improvements (Trevor Norris) >> >> * TypedArrays: Improve dataview perf without endian param (Dean McNamee) >> >> * module: assert require() called with a non-empty string (Felix Böhm, >> James Campos) >> >> * stdio: Set readable/writable flags properly (isaacs) >> >> * stream: Properly handle large reads from push-streams (isaacs) >> >> >> Source Code: http://nodejs.org/dist/v0.9.7/node-v0.9.7.tar.gz >> >> Macintosh Installer (Universal): >> http://nodejs.org/dist/v0.9.7/node-v0.9.7.pkg >> >> Windows Installer: http://nodejs.org/dist/v0.9.7/node-v0.9.7-x86.msi >> >> Windows x64 Installer: >> http://nodejs.org/dist/v0.9.7/x64/node-v0.9.7-x64.msi >> >> Windows x64 Files: http://nodejs.org/dist/v0.9.7/x64/ >> >> Linux 32-bit Binary: >> http://nodejs.org/dist/v0.9.7/node-v0.9.7-linux-x86.tar.gz >> >> Linux 64-bit Binary: >> http://nodejs.org/dist/v0.9.7/node-v0.9.7-linux-x64.tar.gz >> >> Solaris 32-bit Binary: >> http://nodejs.org/dist/v0.9.7/node-v0.9.7-sunos-x86.tar.gz >> >> Solaris 64-bit Binary: >> http://nodejs.org/dist/v0.9.7/node-v0.9.7-sunos-x64.tar.gz >> >> Other release files: http://nodejs.org/dist/v0.9.7/ >> >> Website: http://nodejs.org/docs/v0.9.7/ >> >> Documentation: http://nodejs.org/docs/v0.9.7/api/ >> >> Shasums: >> >> ``` >> fa5771999205beae787e56bbffa3be3c496dbb3e node-v0.9.7-darwin-x64.tar.gz >> 3790a0323e82598d9286470a3ca8b079b25d815c node-v0.9.7-darwin-x86.tar.gz >> 70da0da05a2d76dfba389b413112aa1c31289114 node-v0.9.7-linux-x64.tar.gz >> b7448f020820302a6c648744a9ba4b6e1979fbf8 node-v0.9.7-linux-x86.tar.gz >> a0148c804c37ecbcfd4039213e469ba2757b6125 node-v0.9.7-sunos-x64.tar.gz >> 121cd6fe2fbab0ca20644256914433bfa02ca6c4 node-v0.9.7-sunos-x86.tar.gz >> 8938d57fc9cff896bb13901a43b5cff989785a23 node-v0.9.7-x86.msi >> 23b86861de7c6111311f869c722431cf84d93761 node-v0.9.7.pkg >> 527a86ee094f7ed77967eda3dff4b2aff3f29384 node-v0.9.7.tar.gz >> 5231f327979f900d4ba927f2e63e67635001268c node.exe >> 6a78465d3f6e34aab82a529839c522abbab715ac node.exp >> d814bd0733ba22a3cd9c086d34c68706d6c77663 node.lib >> 5c9df4dcf16c9baafce9b6982907ada586e878a2 node.pdb >> f49f1e0706ef38facba45af75cfdf44678b21f5a x64/node-v0.9.7-x64.msi >> 13f9ee5c81b89bf77c5bfe46993905de4e3384d7 x64/node.exe >> 3f9c67381a7f2b3fc2f6c14b66036dde02de2820 x64/node.exp >> cac98eebe21aeb05741a2fec6e2c7eaf5bb111a6 x64/node.lib >> 563932b95c08ebdb923358cd8b68ee17ac7ad781 x64/node.pdb >> ``` >> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> 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 post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en > > > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > 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 post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > 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 post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
