text stringlengths 0 1.32k |
|---|
**Thomas Watson:** Yeah, I absolutely agree. There was a real problem in Node that had to be solved, and that was of back pressure; there needed to be a way to deal with pressure and to write some sort of -- and I'm not gonna say I know exactly what the solution was, like what minimal type of mechanism was required tha... |
\[31:46\] That said, there's actually a movement right now to move streams (not the Streams 1, 2, 3 - not that JavaScript Streams), to move streaming capabilities down into libuv. Doing that might allow TLS to move into libuv, and other things to move down into libuv, and allow a lot more performance. But even so, even... |
It's terrible... Streams is a huge module, it's very difficult to understand, huge maintenance overhead, and has all kinds of user problems - it has Streams, Cluster, URL... These are big modules that don't have to be there. |
**Sam Roberts:** I think a very easy step that the Node Foundation should take in the documentation is simply just to have the concept of these blessed userland modules that we suggest to people to use instead, because we can't take out Streams of Node Core because everybody's depending on it right now... But at least ... |
**Adam Stacoviak:** So take the soft deprecation approach where you don't remove it, don't disable it, maybe even throw a warning or something like that, potentially... |
**Sam Roberts:** No, don't throw a warning. |
**Thomas Watson:** No, no, no. And don't print anything. |
**Sam Roberts:** No, I consider that breaking. |
**Adam Stacoviak:** Okay... |
**Sam Roberts:** We actually saw that very recently with a change to the buffer API... |
**Adam Stacoviak:** Because you're getting back a result you're not expecting. |
**Sam Roberts:** Yeah, so if I run a module that uses the now deprecated buffer API, it prints out a warning saying "You're running insecure code." The reason in this case was that you could insecurely allocate a new buffer if you didn't know what you were doing. You could also use it correctly, and if you knew what yo... |
People get really scared when they see they see those things when they use your module... So no, definitely not print out anything; in my opinion, that's a breaking change... |
**Adam Stacoviak:** So simply vocalize, "Do not put it in code..." |
**Sam Roberts:** Just update the documentation... |
**Adam Stacoviak:** And then write a blog post on Medium about it...? |
**Sam Roberts:** Oh, you can do a blog post, you can do anything like that, but it's more like an educational process; at least that's the first step. I don't think we'll ever be able to pull out Streams of Node Core. Maybe URL at some point down the line, if we see that less and less people depend on it, I think it's ... |
**Thomas Watson:** \[35:11\] I really like that idea, and actually I might PR a change to the Streams doc right away. I mean, Streams needs to be documented in Node because Node APIs return Streams, you have to know what the APIs are. But there's a very good argument that you should never yourself type "require Stream"... |
**Adam Stacoviak:** That's what it says for -- is it \[punny\] or \[pewny\]? |
**Thomas Watson:** \[pewny\] code. |
**Adam Stacoviak:** \[pewny\] code? I thought it was \[punny\] code... |
**Thomas Watson:** It's \[pewny\], because it comes from Unicode. |
**Adam Stacoviak:** Okay, gotcha. And it actually says, "Users currently depending upon the puny modules should switch using the userland provided at punycode.js module instead." So they're already taking these steps, like you're suggesting. |
**Sam Roberts:** That's cool, I haven't seen that. That's really awesome. That means that it's not really that big of a political issue apparently to do that. |
**Adam Stacoviak:** So your suggestions are already being accepted, to a degree. |
**Thomas Watson:** Yeah, so with Readable Streams it's a little bit different, because you can't not use Node streams. I mean, when you do fs.createWriteStream you are getting back a Node stream, right? But we can't nudge people to not use it themselves, to use Readable Stream directly. Well, I mean, directly from npmj... |
**Adam Stacoviak:** Any final closing thoughts? |
**Sam Roberts:** I'll just say no. |
**Adam Stacoviak:** Alright, thanks fellas. |
**Thomas Watson:** Thank you! |
\* \* \* |
**Adam Stacoviak:** Thanks again to our friends at the Linux Foundation and the Node Foundation for working with us on this project, as well as our friends at IBM and StrongLoop for sponsoring this podcast series. It was a blast being there. |
We'll be there again next year, so look out for us in 2017 at Node Interactive. If you wanna hear more JavaScript-focused podcast from Changelog, check out JS Party, our new live weekly show with Mikeal Rogers, Alex Sexton and Rachel White. Head to Changelog.com/jsparty, click Subscribe, don't miss a show, and thanks f... |
• The importance of Node to Microsoft |
• VM neutrality and its benefits for developers |
• Chakra and ChakraCore: a high-performance JavaScript engine and its relationship to Node |
• Why Microsoft forked Node and created ChakraCore |
• IBM's involvement with Microsoft in promoting Node with VM neutrality |
• ChakraCore is the core part of the Chakra JavaScript engine |
• Chakra engine powers Edge browser and Windows 10 |
• ChakraCore is cross-platform and open source |
• Open sourcing ChakraCore allowed for community engagement, innovation, and growth |
• The decision to open source was motivated by a desire to help the community, allow developers to use the technology, and reach a wider audience |
• Technical steps to open source were minimal due to existing work on modern hosting API and supporting Windows 10 IoT platform |
• Chakra is used in various Microsoft products including Azure DocumentDB, Outlook.com, and others |
• Future plans include taking Chakra cross-platform |
• Chakra engine available on Linux and Ubuntu x64 versions, with a Mac OS X preview |
• Goal of parity between Windows and other platforms for functionality, performance, and characteristics |
• Time-travel debugging innovation being developed in collaboration with Microsoft Research |
• Open sourcing of ChakraCore code on GitHub, with MIT license and open documentation |
• Community involvement encouraged through GitHub issues, roadmap transparency, and contribution opportunities |
• Cross-platform development efforts for Node ChakraCore and Nappy (Node.js API) layer stability guarantee |
• Ways to get involved: try new technology, file issues, report problems, contribute code, or join the API Working Group |
• Node Core project and API Working Group discussed |
• Nappy (N-API) project mentioned, goal is to create stable Node API for module developers |
• Need community help to convert native modules onto new API |
• VM neutrality and its importance |
• Microsoft's involvement in Node and ChakraCore |
• Azure as a cloud platform for Node development |
• Efforts to improve developer experience with VS Code, TypeScript, Docker, and app insights |
**Adam Stacoviak:** \[00:31\] Welcome to our Spotlight Series titled The Future of Node, recorded at Node Interactive 2016 in Austin, Texas. We produced this in partnership with the Linux Foundation, the NodeJS Foundation, and it's sponsored by IBM and StrongLoop. |
**Break:** \[00:44\] |
**Adam Stacoviak:** In this episode we talked to Gaurav Seth, lead program manager of Chakra and TypeScript, as well as Arunesh Chandra, program manager of ChakraCore. We talked about their polite fork of Node to introduce the community to Chakra, the high-performance JavaScript engine that powers Microsoft Edge. We al... |
Let's start out with "Why Node inside of Microsoft?" Why is Node important to Microsoft? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.