text stringlengths 0 1.32k |
|---|
**Adam Stacoviak:** No worries. |
**Rachel White:** So, "The Tessel 2 is a robust IoT and robotics development platform that leverages all of the libraries of NodeJS to create useful devices in minutes." It has a ton of stuff already on it, which is great, too. Before, you would need to get just a regular Arduino that doesn't have Wi-Fi, and you have t... |
I'm really good at speaking vaguely, but it has a ton of stuff already built on it - it has two USB ports, Wi-Fi, it has an Ethernet core if you need it, it's super fast... I've only done a little bit of work with it, but I know a lot of the people that are involved in the development community for it are working super... |
I think that it's only gonna help especially the Johnny-Five community grow even more. Because before, we would have to rely on Chris Williams' voodoospark firmware - which was great, and that's the first thing that I tried hardware on. That's what I had to install to get hardware to work with Node, but now there's suc... |
**Adam Stacoviak:** \[31:16\] Yeah. Any closing thoughts? This is, like I said, The Future Of Node Series - we're trying our best to inform and encourage the community to try new things, to get involved. |
**Rachel White:** Yeah. If you're thinking of making something but thing that people might not like it, do it anyway, because you're never gonna know unless you try. I heard a quote from David Lynch once that was in regards to his films - when he has a vision, all of the creative process that he has that goes into it i... |
**Adam Stacoviak:** Totally... |
**Rachel White:** ... and I think that that's something that a lot of people don't think about, and I just want them to try. |
**Adam Stacoviak:** It's a good message. |
**Rachel White:** Yeah. |
**Adam Stacoviak:** Thank you. |
**Rachel White:** Thanks. |
**Adam Stacoviak:** It was nice talking to you. |
**Rachel White:** Yaay! \[laughs\] |
• io.js fork from Node in 2014 |
• Formation of the Node Foundation with Linux Foundation and initial governance model |
• Merger of io.js back into Node and iteration on governance policies for LTS releases |
• Growth of contributors, diversification of contributor base, and increasing overall contributor count |
• Shift from proof-of-concept to sustainability strategy and increased focus on community contributions beyond just code |
• Comparison with other platforms such as Swift, Rails, Phoenix, and Elixir on community structure and contributor diversity |
• Measuring Node.js growth and success against its own ecosystem, rather than comparing it to other languages |
• Node.js user community has quadrupled in size since the io.js fork, reaching 5.7 million users |
• Growth is attributed to JavaScript itself, with many people using Node.js for various applications beyond server-side development |
• The community is broadening its view of what Node.js is used for, including IoT, frontend frameworks like React, and desktop applications |
• Challenging issues include keeping things simple and easy-to-use, and providing educational materials for new users |
• The Linux Foundation's support has enabled new initiatives such as childcare services and diversity efforts at the NodeConf conference |
• The community has benefited from institutional support, allowing them to provide resources that were previously unavailable. |
• Discussing the importance of inclusivity and diversity in community conferences |
• The use of colored stickers to indicate preferences for photography or approachability |
• The role of Tracy in pioneering diversity and inclusivity work in community conferences |
• The benefits of VM neutrality, including increased competition among VM developers and improved performance for users |
• The open sourcing of ChakraCore and its potential impact on the Node.js ecosystem |
• The collaboration between Microsoft and other companies to improve Node.js development and user experience |
• Creating a stable API in Node.js to enable VM neutrality |
• Importance of the Node Foundation in bringing together stakeholders for long-term support |
• Transition from BDFL governance model to open governance model with the creation of io.js |
• Growing community needs and limitations of Joyent's stewardship of Node.js |
• Value of Rod Vagg's leadership in establishing a more inclusive and open governance model |
• Increased committer numbers (from 5 to almost 100) |
• VM neutrality benefits for IoT development, including new JavaScript VMs on-device |
• Node serial testing matrix is slow and outdated |
• Importance of security in the Node ecosystem |
• Lift Security's Node Security Project and its integration into the Node Foundation |
• Creation of a new working group for responsible disclosure of security vulnerabilities |
• Concerns about the diversity and quality of packages in the Node ecosystem |
• Need for formal education and certification programs for developers |
• Plans to develop a baseline Node.js certification program with The Linux Foundation |
• Discussion of Athan Reines' open source project, Standard Lib, for data science in JavaScript |
• Challenges in Node.js for math and scientific computing due to lack of language-level tools |
• Efforts by Mikeal Rogers and the Node Foundation to resolve standards issues through TC39 meetings |
• Importance of reaching a system like R and Python have for scientific computing in JavaScript |
• Modular ecosystem development for 3D computing using WebGL, Regl, and ndarray |
• Comparison with SciPy and R's approach to binding Fortran libraries |
• Nurturing developers working on open source projects through community building and outreach |
• Passionate individuals at academic institutions driving Node.js adoption |
• Need for a venue for developers to share knowledge and experiences |
• Growth of the Node community and its challenges |
• Importance of supporting module developers and experimental projects |
• Diversity in the Node community as an important consideration |
• Focusing on serverless capabilities and resource utilization improvements |
• Potential for more assertive messaging about Node's strengths |
**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 Node.js Foundation and it's sponsored by IBM and StrongLoop. |
**Break:** \[00:43\] |
In this episode I talk with Mikeal Rogers about some of the back-story of Node over the past few years to get to where we are today. We talked about io.js, the fork of Node, what's happened in the community and the code since that timeframe, how the Node Foundation has helped to solidify the foundation on which the Nod... |
**Adam Stacoviak:** Where to begin, man? I think the last time we had a deep conversation like this was in the io.js/Node fork timeframe; we had you on the Changelog, talking about the rise of io.js. That was a good thing at the time, because it helped a lot of the community to have some power it didn't think it had, a... |
**Mikeal Rogers:** Yeah, I think also we were able to adopt some governance practices that were relatively new. They were based on some ideas that we had tried out in the ecosystem, like liberal contribution agreements and stuff like that, but no project of that size had ever done it... So the argument that "You should... |
**Adam Stacoviak:** That's about nine months after? |
**Mikeal Rogers:** No... They announced it about a month after we announced io.js. |
**Adam Stacoviak:** What year was this? 2015, right? Not this year. |
**Mikeal Rogers:** Yeah, 2015. The day after Thanksgiving 2014 was when we announced io.js, and then in January 2015 there was a Node Summit conference and they announced that they were forming the foundation then. Foundations take a long time to really get off the ground and get the ball rolling... |
**Adam Stacoviak:** Announcing it and launching it is two different things. |
**Mikeal Rogers:** Yeah, so they announced intent to form, they had some initial members signed up, but they needed more members. Those members, in turn, wanted to put the fork to bed and bring a merger in... So I negotiated with the foundation and the io.js community to kind of bring everything in and merge the projec... |
\[03:48\] Even just merging into Node required us to immediately iterate on a lot of these policies. In io.js we really didn't have to worry about a lot of backwards compatibility or breaking changes and things like that. Because it's a new project, not everybody's already depending on it; you can do a lot more. So whe... |
We have a really liberal policy about getting stuff into master and making some changes, then we have a really good cycle and a longer review process to get things into the LTS releases that enterprises depend on. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.