I understand. I'm just being contrary. > Node has tried to be very strict about what he version means from the beginning. pre-1.0 means "stable, but not done".
God forbid it should ever be "done", whatever that means. I doubt there will be much difference between v 0.999 and v 1.001. On a more serious note, what harm does .exists do? http.createServer violates all the rules and it is the first thing a node newbie sees. On Wed, May 30, 2012 at 5:47 PM, Marco Rogers <[email protected]>wrote: > Yes I know that. But that is despite the pre-1.0 version. Node has tried > to be very strict about what he version means from the beginning. pre-1.0 > means "stable, but not done". Some people think "stable" means "we won't > break backwards compat". But I'm suggesting that it actually mean "we'll > try really hard for backwards compat, but we might break things for the > good of the api". I think in the case of path.exists, this is very doable. > If we can't do stuff like this now, then we are resigning ourselves to > being stuck with these warts forever. And path.exists/fs.exists is a > particular bad wart because it's the exact place people will look for this > functionality. So the propagation of this will continue to go up. > > :Marco > > > On Wednesday, May 30, 2012 5:11:37 PM UTC-7, Mark Hahn wrote: >> >> It's like google's "beta" gmail was. >> >> On Wed, May 30, 2012 at 5:11 PM, Mark Hahn <[email protected]> wrote: >> >>> The ver 1.0 moniker is pretty much meaningless. Many many people have >>> it in production. >>> >>> >>> On Wed, May 30, 2012 at 4:49 PM, Marco Rogers <[email protected]>wrote: >>> >>>> If you're using a pre-1.0 platform, your code is subject to breakage. >>>> Also you have to opt into upgrading and every major node update has >>>> required minor changes. >>>> >>>> At some point we went from changing the node api a lot to make it >>>> better to not changing it at all for fear of crying developers. I'm not >>>> suggesting we open flood gates. I'm suggesting we continue to refine the >>>> api and get as close to one with no unnecessary warts as we can before >>>> going 1.0. Because then we really are screwed. >>>> >>>> :Marco >>>> >>>> >>>> On Wednesday, May 30, 2012 3:45:53 PM UTC-7, Mark Hahn wrote: >>>>> >>>>> I would be very unhappy if someone broke my code. Ask the jquery bdfl >>>>> what happened when he tried to make a non-backwards-compatible change. >>>>> >>>>> -- >>>> Job Board: http://jobs.nodejs.org/ >>>> Posting guidelines: https://github.com/joyent/**node/wiki/Mailing-List- >>>> **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 >>>> nodejs+unsubscribe@**googlegroups.com<nodejs%[email protected]> >>>> For more options, visit this group at >>>> http://groups.google.com/**group/nodejs?hl=en?hl=en<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
