[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8},"actionData","errors","root",{"_11":-5,"_53":54,"_55":56,"_57":58},"routes/user.$name.topics",{"_9":10,"_11":12,"_13":14,"_15":16,"_17":18,"_19":16},"topics",[35],"user",{"_20":21,"_13":14,"_22":23,"_24":25,"_26":27,"_28":29,"_30":16,"_31":32,"_33":34},"loginname","piaohai","page",1,"limit",20,"total","id","2286","avatar_url","http://www.gravatar.com/avatar/879ae026feca649d3f4f17b47be6194d?size=48","githubUsername","","create_at","2012-02-01T10:24:11.005Z","score",25,"topic_count","reply_count",4,"is_star",false,{"_20":36,"_37":21,"_38":-5,"_39":40,"_41":42,"_43":44,"_45":34,"_46":34,"_31":47,"_48":49,"_26":50,"_51":52},"181","author_id","tab","content","

好吧，我承认，这个标题有点暧昧的基情，但是希望下文的内部能给不熟悉或不喜欢Shell或WIN平台下的批处理编写的工程师带来一些帮助。

\n\n

首先，我承认Shell脚本配置sed,awk等工作已经相当强大了，熟悉的朋友就对下面的内容一笑而过吧，但是如果你喜欢上了NODE，那就让我们继续旅程吧：

\n\n

好吧，先做一段简单的Shell得到时间差代码的冷菜diff.sh：

\n\n

#!/bin/bashSTART=$(date +%s)\n# 洗菜之类的事先准备吧\ndu -m /home > /tmp/output\n# 吃完了\nEND=$(date +%s)\nDIFF=$(( $END - $START ))\necho \"化了$DIFF 秒搞定\" \n\nchmod +x diff.sh\nsh diff.sh\n

\n\n

执行结果如下：

\n\n

化了0 秒搞定\n

\n\n

～o,能吃这么块吗，难道BUG了吧，好吧，是速度太快了，只是脚本中采用的是秒数级别的范围，估计只能用纳秒也进行，并在Shell做除法运算。好吧，再采用NODE试一把看看vim diff.js：

\n\n

#!/usr/bin/env node\nvar util  = require('util'),\n    spawn = require('child_process').spawn,\n    ls    = spawn('du', ['-m','/home/']);\nvar start = +new Date();\nls.stdout.on('data', function (data) {\n//console.log('stdout: ' + data);\n});\n\nls.stderr.on('data', function (data) {\n  console.log('stderr: ' + data);\n});\n\nls.on('exit', function (code) {\n  var end = + new Date();\n  console.log(end-start);\n});\n

\n\n

执行一下./diff.js：

\n\n

1113\n

\n\n

时间直接显示是毫秒级别，是不是感觉更舒服些，好吧，我承认做这样的比较，并不是说要一决高低，只是用前端攻城师喜欢的方式工具去做菜，依赖于Shell的强大功能基础之上，当然喜欢不同的语言的攻城师也可以用Python,Ruby之类的语言去实现。

\n\n

好的，如果你觉得有趣，那就接着跟着我向前，否则就直接拍砖吧，哈哈。

\n\n

以上示例可以看到，借用Shell脚本，NodeJs内置功能做一些常用的小菜是很方便的而且很灵活，Shell脚本功能的强大之为就是流的重定向处理等,是不是需要采用写成脚本或直接如果采用一采超复杂的命令来搞定，呵呵，对我们之为的非系统管理员可能有一定的难度，好，那就拿出强大点的菜刀procstreams，看看它是怎么做菜的吧：

\n\n

#!/usr/bin/env node\nvar p = require('procstreams');\np('cat app.log').pipe('wc -l')\n  .data(function(stdout, stderr) {\n      console.log(stdout);\n  });\n

\n\n

上面的JS代码是实现统计app.log的行数，相当于Shell的cat app.log | wc -l功能，感觉怎样，如果要实现复杂或交互的功能，会不会更灵活些呢。再上一菜

\n\n

#!/usr/bin/env node\nvar p = require('procstreams');\n    p('mkdir foo')\n       .and('rm file.txt')\n          .on('exit', function() {  \n                console.log('done');  \n           });\n

\n\n

是不是很熟悉的感觉？\n 如果执行脚本的时还需要处理复杂一些的参数对应的问题，怎么办？没关系，node-optimist 及 isaacs's nopt 之类的工作早就等着你们这类的攻城师呢？\n再上最后一道菜：

\n\n

#!/usr/bin/env node\nvar util  = require('util'),\n  spawn = require('child_process').spawn;\nvar argv = require('optimist').argv;\nvar cmd =  argv.cmd;\nvar args = argv.args\nvar option = argv.opt\nconsole.log(cmd + '  ' + args + '  ' + option);\nvar ls    = spawn(cmd , [args ,option]);\nls.stdout.on('data', function (data) {\n  if (!data || !!data)  console.log(' i believe it');\n});\n\nls.stderr.on('data', function (data) {\n  console.log('It\\'s a miracle!');\n});\n\nls.on('exit', function (code) {\n   console.log('it.justHappened();');\n});\n

\n\n

～亲，谢谢你，一直走到了最后，以上只是个人在工作写有些写Shell脚本时常因为一个空格或格式之类的情况查找半天而抓狂不已，以后采用和NODEJS结合会不会更淡定些，请各各抒己见，欢迎拍砖吧。

\n\n

参考资料：
\nhttp://nodejs.org
\nhttp://www.catonmat.net/blog/

","title","当Shell遇上了NodeJs","last_reply_at","2016-03-14T15:54:55.104Z","good","top",8,"visit_count",18348,"2012-02-02T06:38:56.941Z","author",{"_13":14,"_22":23},"zones",[103],"tabs",[72,73,74,75,76,77],"publicConfig",{"_59":60,"_61":25,"_62":63},"apiBaseUrl","https://api.cnodejs.org","turnstileSiteKey","build",{"_64":65,"_66":67,"_68":69,"_70":71},"service","cnode-web","version","0.1.0","commit","9ab83f39eed6b4a14eedbb8fbadfefe40dba3d45","buildTime","2026-07-30T19:01:36Z",{"_20":16,"_79":101,"_81":102,"_83":93,"_84":16,"_86":94},{"_20":98,"_79":99,"_81":100,"_83":93,"_84":98,"_86":94},{"_20":95,"_79":96,"_81":97,"_83":93,"_84":95,"_86":94},{"_20":32,"_79":45,"_81":92,"_83":93,"_84":32,"_86":94},{"_20":88,"_79":89,"_81":90,"_83":34,"_84":91,"_86":87},{"_20":78,"_79":80,"_81":82,"_83":34,"_84":85,"_86":87},10,"key","test","label","测试","visible","sort_order",91,"scope","admin",9,"dev","开发",90,"精华",true,"public",3,"job","招聘",2,"ask","问答","share","分享",{"_20":16,"_104":105,"_106":97,"_107":108,"_109":110,"_83":93,"_84":16},"slug","jobs","name","description","Node.js 招聘信息专区","icon","briefcase"]