Datasets:
text stringlengths 0 1.36k |
|---|
• Discussion of Node.js user survey results |
• Breakdown of Node.js users' focus (back-end, front-end, full stack, etc.) |
• Use of containers among Node.js users |
• Comparison between front-end and back-end usage in Node.js |
• Analysis of npm downloads and dependencies |
• Mention of China as a significant growth market for Node.js |
• Concerns about relying on download metrics as a measure of usage and adoption |
• Discussion of the limitations of download metrics in quantifying people's engagement with packages |
• Introduction of npm's user metric, which is based on website impressions over a three-month period |
• Use of NodeJS.org website metrics to understand geographic distribution of Node users |
• Identification of a gap in data for independent users in China and how it was addressed using cnodejs.org forum metrics |
• Skepticism about the impact of build tool usage on metrics and the need for further analysis |
• Analysis of GitHub data to split front-end and back-end package engagement |
• Discussion of challenges in determining whether users are engaged with Node.js as a build tool or for server-side use |
• Node.js adoption in enterprises |
• Shift to front-end development with Node.js |
• Benefits of Node.js for cross-platform development |
• Comparison of Node.js with other languages (e.g. Python, Ruby) |
• MongoDB usage and its performance issues |
• Stripe's experience with MongoDB and its limitations |
• Development of Secure Scuttlebutt as a peer-to-peer social network |
• Need to create a platform that allows other developers to build on top of Secure Scuttlebutt's technology |
• Idea to use Electron and Chromium to build an entirely new browser with decentralized protocols |
• Research into various decentralized protocols, including IPFS and Dat |
• Focus on integrating Dat due to its ability to handle data that changes over time |
• Decision to focus on one protocol (Dat) instead of trying to support multiple protocols simultaneously |
• Current state of Beaker browser and its integration with Dat protocol |
• Dat peer-to-peer techs allow creating websites directly from a computer using a browser |
• Key features: better personal privacy, open source architecture, no reliance on centralized services or databases |
• Security concerns: malicious individuals could potentially control content by pretending to be multiple users, but the system is designed to prevent this through use of public-private key pairs and signature verification |
• Public keys are 64-character hex strings, making them difficult to recognize and spoofing more challenging |
• Dat addresses piggyback on HTTPS servers using a well-known folder for verification, providing a compromise solution until further security measures can be implemented |
• The Code For Science team is grant-funded by organizations such as the Knight Foundation and Sloan Foundation to develop the Dat protocol |
• Hashbase is a public super-peer network allowing users to upload files without relying on others to seed them |
• Centralization vs decentralization: Paul Frazee argues that centralization can be a necessary step towards decentralized systems, citing Hashbase as an example |
• Future plans include allowing users to run their own decentralized servers at home for improved privacy and control |
• Picks: |
• Alex Sexton recommends GlobalizeJS for internationalization |
• Mikeal Rogers recommends Semantic Release for automating module releases |
• Paul Frazee recommends the TV show Game of Thrones |
**Mikeal Rogers:** Welcome to JS party, where it's a party every week with JavaScript. I'm Mikeal Rogers. |
**Alex Sexton:** I'm Alex Sexton. |
**Mikeal Rogers:** And our guest today is Paul Frazee. Say hi, Paul. |
**Paul Frazee:** Hey, everybody. |
**Mikeal Rogers:** Awesome. So we've got Paul on to talk about the Beaker Browser, which we'll get into a bit later, but first we're just gonna discuss this new Node.js user survey. Everybody heard about Node.js, everybody know what that's about? |
**Alex Sexton:** Only if it's pronounced NodeDotJs... |
**Mikeal Rogers:** Yes, NodeDotJs. There actually is somebody very prominent who always says it that way... It just takes too long to say. I think that we can just call it Node. |
Anyway, so there was this great Node.js user survey; about 1,400 people were surveyed at the end of 2016. It took quite a while; I was still at the Foundation while this was happening, obviously, so it took a while to synthesize the results, but now finally all of the results and some big summaries and all the data are... |
Any initial thoughts or remarks about this from you all? |
**Paul Frazee:** Kind of interesting, 50% of people are using containers... That's a nice little insight there. |
**Mikeal Rogers:** I always forget -- not everybody has listened to every podcast where we've talked about a survey, but there's a really good issue of the Changelog, actually, where me and Nadia came on and interviewed somebody about the GitHub survey... And one of the things that we got into was that it's very import... |
One really good thing in Node is because you know that the community is doubling every year, if you ask people how long they've been doing Node, you'll get a really good idea of what the distribution is of the people that you ended up surveying. With stuff like this you tend to get people that have been using the langu... |
**Paul Frazee:** Do you think it should be more, or less? |
**Mikeal Rogers:** Well, I think it's surprising just in that there's a lot of people using Node.js and just doing front-end stuff, and a bunch of them showed up in this. A big portion of the 50% that said no to containers just aren't doing any back-end stuff... |
**Paul Frazee:** Right, right. |
**Mikeal Rogers:** \[03:57\] And how many of them are just deploying with Now and they don't even know that that's in a container, right? There's already a lot of services that are like -- the containers are so hidden from you and so pushed down in the stack that you don't even know. Yeah, so that was a bit surprising.... |
I'm glad that the Foundation is talking about China a bit more. I tried to talk about this, but China is the fastest-growing section of Node.js users, and probably just developers in the world, to be honest. It's crazy. There are a lot of users in China. There's like over a million Node.js users in China now, which is ... |
**Alex Sexton:** We have a link that we'll probably share on the page if you're reading the summary, or something... The Hacker Noon kind of rolled up with some of the things, and I feel like they asked some questions about -- or rather they have like 39% of respondents are using containers for front-end development. T... |
**Mikeal Rogers:** Well, you could figure it out from the data, though... Because they shared the data. There's a graph here that basically says "What is your focus?" and there's Back-end, Full Stack, Front-end, DevOps, Desktop Applications, Mobile, IoT and Security. |
**Alex Sexton:** Right, that's their job; they might program Python and then use Node for developer tools \[unintelligible 00:06:09.07\] |
**Mikeal Rogers:** Yeah, so these are all just checkboxes, right? What you really wanna know is how many people checked the front-end box and not the full stack or back-end box. How many people only checked the front-end box? That's the one we wanna know, right? |
**Alex Sexton:** No, I don't need -- like, I'm a full stack developer, but I don't write Node servers at my job, like I do for fun, or whatever. But at my job, Stripe is a Ruby stack for the most part, so I mostly write Ruby if I'm writing back-end. So I would consider myself a full stack developer, but my day-to-day i... |
**Mikeal Rogers:** Well, it looks like this question was posed in the context of using Node.js, not in the context of like "What kind of developer are you?" |
**Alex Sexton:** I would be interested in the exact wording... |
**Mikeal Rogers:** I believe the wording was "How was your organization using Node.js? What is the focus of your Node.js usage, specifically?" |
**Alex Sexton:** Okay. |
**Mikeal Rogers:** Yeah, which is like -- full stack is just such a weird one, because it's like... If you click back-end and front-end, is that not just full stack? \[laughter\] Yeah, but it's interesting that the full stack metric here actually outpaces the front-end metric. |
**Paul Frazee:** What would you think it means if I just say I use Node.js for my front-end? |
**Mikeal Rogers:** I like the desktop application, mobile and IoT stuff was on here too, because it makes front-end really mean JavaScript front-end. If your front-end is an Electron app, you're gonna click the desktop application box... So that's great. |
**Alex Sexton:** \[07:55\] Mikeal, I know you used to have numbers on downloads, but it still feels like based on what gets downloaded from npm, that over 50% of all use of npm is for building front-end tooling, right? |
End of preview. Expand in Data Studio
2017 JS Party Transcripts
Complete transcripts from the 2017 episodes of the JS Party podcast.
Generated from this GitHub repository.
- Downloads last month
- 196