https://www.nginx.com/blog/launching-nginscript-and-looking-ahead/

美国服务器http://hg.nginx.org/njs
WTF!

不得不说老毛子果然是战斗民族

Niubility.

https://github.com/syncninja/syncninja

用 js 来配置 nginx ？ 是这样理解么……

这功能。。。不错

简直前端狗的春天.

lua 怎么办，有必要又造一个轮子吗？

nodeGINX 要出现了？

OpenResty 表示压力很大。

表示期待

We run a separate VM for each request, so there ’ s no need for garbage collection.
谁敢做下小白鼠？

感觉好你还的样子。
nginScript

这很好啊，和第一语言 php 一样的运行模式

+1

我说 nginx 的 wiki 咋改版了呢

不是作为一个模块而是直接嵌入到里面么？

好棒(/≧▽≦/)

评论褒贬不一啊
```
You're using JS, which helps the expressivity issue a bit, but in exchange it's inheriting all the problems of JS, and squishing them into my web server, and with no apparent framework for making common and dangerous tasks simple and safe.
For example, the comment in your second says that unary + applied to a string will "convert upstream number to integer", but that's not true. It converts a String to a Number (including the "number" NaN). +"0.5" is the Number 0.5, which will send you to the server "my_upstream0.5". +"X" is NaN, which will send you to "my_upstreamNaN". Unary + supports scientific notation, too, so "1.2e-100" becomes "my_upstream1.2e-100". It supports hexadecimal integers, too, though that's less interesting when you clamp to [0,1].
These mis-routings are probably harmless in this case, but it's not hard to imagine similar situations where they're not.
If the authors of a feature can't use it safely in their trivial demo examples in the product announcement, what confidence do I have that I'm going to be able to make it work reliably and securely on an actual production website?
--JS Dude
```

貌似开发者的意思是希望这东西仅仅用来配置 nginx 服务程序，而不是做出一个完整的服务。和 OpenResty 之类还是有分别的。

世界是 javascript 的