On Thu, Aug 22, 2013 at 2:22 PM, Eldar <[email protected]> wrote: > > Be conservative in what you send, be liberal in what you accept. > > This is absolutely wrong! You should be conservative in what you accept > and conservative > in what you send otherwise you get huge troubles, shits and endless "it > works here doesn't there" story. > Browsers are good example. >
This is so misguided it's not even funny. There's a huge difference between being liberal and having defined results for every input and the bullshit that went on during the major browser wars. >people writing node modules should follow the node patterns and never mix > sync and async behavior > > There is a certain edge between the case when you should follow common > practices event if you don't like them > and the case when you shouldn't, because they are so bad that cause a > greater damage > than confusing people from time to time. > You realize that if you want to be conservative as an API developer, you need to use nextTick(), right? There's absolutely zero change of danger or confusing when forcing async callbacks. All of the danger and confusion comes from sometimes-sync callbacks. > For the case of nextTick I ignored it, because it's such a PITA. > Sorry that writing one more line of code is so troublesome for you. -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
