+1. It already got moved from "path" to "fs" and people did adjust to the change. Why not shake it one more time and fix it (or remove it)?
On Sunday, August 19, 2012 12:01:54 PM UTC+2, Robert Gould wrote: > > Node has broken backwards compatibilty before and will in the futre, why > not just deprecate fs.exists and remove it in 0.9? As THE black sheep in > node.js it does more hurt by being there, then not being there. Not needed > and not much use beyond being an insider joke for people that have been > around from the start -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
