Not just "brand new" (8 hours ago), but "experimental" (which means it's not available by default in stable Chrome versions yet).
And yes, it is more or less what we discussed with Google more than 2 years ago
, but it comes with several limitations and caveats (cross-frame permissions inheritance, blind redirects and so on...)
Furthermore, even if it was safe and ready for prime time (and it is not yet), there's lot more in NoScript aside script blocking (e.g. ClearClick, andvanced XSS filters, HTTPS enhancements or ABE) which can't be done in Chrome yet.
However, maybe we're gonna have a proper "NoScript Lite" for Chrome (branded as such and developed by me) by the end of this year