text stringlengths 0 1.32k |
|---|
**Shiya Lou:** I think once a day, or so. So remember the ZPad thing? |
**Adam Stacoviak:** Yeah, LeftPad. |
**Shiya Lou:** Yeah, LeftPad - it never affected China because when it happened we were like, "Oh, let's just stop mirroring that part. Let's just not sync that part." |
**Adam Stacoviak:** Wow. That's an easy way to avoid it. For those who aren't familiar, give us the deeper side of Cnpm. It's a mirror of the registry... What's the point of it? Is it because of the firewall? |
**Shiya Lou:** Yeah, it's because it's much slower to download... |
**Adam Stacoviak:** From elsewhere. |
**Shiya Lou:** From npm, yeah. |
**Adam Stacoviak:** So who got the permission to synchronize this? Did they work with the government, did they work with somebody to bypass parts of the firewall to sync the registry? |
**Shiya Lou:** So the firewall doesn't work in a way that you need permission to do things; you just do it until someone stops you. So npm right now does not have anything political, basically, so there's no reason to censor it. And it's very important for the developers, so that's a very... |
**Adam Stacoviak:** So basically until it may cross a line that should not be crossed, door are open. |
**Shiya Lou:** Right, yes. |
**Adam Stacoviak:** How does that make you feel? Does that make you happy/sad? That's gotta make you sad, right? |
**Shiya Lou:** Yeah, I am completely against it. I think most people, or most of my developer friends are against it, too. I have met a couple of people who have been working on this project, which I don't call them friends... \[laughs\] I think most people - if you work on this project, you could probably find a bette... |
**Adam Stacoviak:** I'm just kind of curious, if someone from China -- because you still live there? You live in the U.S. now, right? |
**Shiya Lou:** \[24:05\] I'm still living in China for another month or so. |
**Adam Stacoviak:** Okay, gotcha. So would you get in any trouble if someone from China heard you talking like this, or just in general sharing information about how things work? |
**Shiya Lou:** I think the extent of what I've been talking about is pretty mild, so I shouldn't get in any trouble for this. |
**Adam Stacoviak:** But it's possible. |
**Shiya Lou:** Yes. |
**Adam Stacoviak:** What I'm trying to get at is that the listeners listening to this should be thankful that you're sacrificing potentially, to some degree. |
**Shiya Lou:** Yeah. |
**Adam Stacoviak:** I'm not sure what level of sacrifice there is, but there's some concern for you. |
**Shiya Lou:** Well, yeah, but I think this is pretty common knowledge already, so that's fine for me to talk about. It's pretty open... Everyone kind of knows about this now. |
**Adam Stacoviak:** Okay. So for those who are right now in China, listening to this podcast - maybe we've got a hundred people; it's a big country, a lot of people there, maybe it's 10,000 people, I don't know... What do they need to know about Cnpm? What do they need to know about this concern you have of the firewal... |
**Shiya Lou:** Well, I think it's definitely more beneficial to learn English, because you're far ahead of people who have to wait and read Chinese documentation. I think that's actually the bottleneck for developers in China - not being able to be updated so quickly with English documentation. |
**Adam Stacoviak:** You need to hear you say that; I wouldn't expect you to say that it'd be just easier to learn English, because it seems like it's part of your culture, your heritage, where you're from, to keep and maintain, rather than to give up. |
**Shiya Lou:** Can you repeat that? |
**Adam Stacoviak:** It wasn't really a question, I was just empathizing with you that I find it a little sad that the bottleneck is the translation, that the bottleneck is being forced to some degree, learning or speaking English. |
**Shiya Lou:** Well, so computer programming is basically in English, so everyone is kind of forced to learn English. |
**Adam Stacoviak:** I guess that's true, I'll take that back then. I'm not empathizing, I'm just kidding. \[laughter\] I'm a fan of Ruby - my roots are in Ruby, huge fan of Yukihiro Matsumoto, or Matz, as we know him, the creator of the Ruby language... Native Japanese speaker - he speaks Japanese as his primary langua... |
I'm not really sure what my question was, I've caught myself rambling. That's really all I have. Did you have anything you wanted to share with the Node world that I may not have asked you? |
**Shiya Lou:** No, I think we have covered it, really. |
**Adam Stacoviak:** Okay, I'll stop rambling then. Thank you, I appreciate it. |
**Shiya Lou:** Okay. |
• Keeping Node Core small and modular |
• Limiting features added to Core to prevent breakage and promote stability |
• Encouraging more modules and less in-Core functionality |
• Addressing issues with pre-packaged dependencies and the inability to choose specific module versions |
• Considering removing certain libraries from Node Core, such as URL and Promises |
• Discussing solutions for handling dependencies and breaking changes when removing or changing libraries |
• Adding a WHATWG compliant URL parser to Node's internals for consistency |
• Vendoring in third-party modules instead of duplicating functionality |
• Deprecation and removal of Node's built-in URL library |
• Using npm-installed versions of libraries for userland code instead of built-in ones |
• Punycode module being deprecated and possibly removed due to low usage |
• Concerns about breaking changes if removing or deprecating the URL library |
• Criteria for determining what should be in Node Core vs userland modules |
• Deprecating and removing outdated or obsolete modules |
• HTTP/2 module, including potential performance benefits and implementation challenges |
• Pre-built binaries for Node ecosystem to facilitate easier installation of native dependencies |
• URL library deprecation and replacement with a better version |
• Websocket APIs and their relationship to Node Core vs userland modules |
• Node HTTP API and its complexity |
• Tradeoffs between performance, implementation ease, and maintenance costs |
• HTTP/2 protocol implementation and its implications for Node |
• Streams module: design issues, user problems, and alternative solutions |
• Soft deprecation approach for deprecated modules (e.g. Streams) |
• Potential movement of streaming capabilities to libuv |
• Maintenance and documentation strategies for Node Core |
• Changing the API to force correct usage of Streams |
• Potential breaking changes causing issues in dependent modules |
• Documentation updates as a solution |
• Educational process (blog post, etc.) to inform users about the change |
• Plans to eventually remove Streams from Node Core |
• Readable Streams documentation improvement |
**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 series in partnership with the Linux Foundation, the Node.js Foundation, and it's sponsored by IBM and StrongLoop. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.