Conference showcases enterprise development best practices, new innovation and emerging standards for JavaScript technologies

SAN FRANCISCO, June 7, 2018 – The JS Foundationand Node.js Foundationtoday announced the initial keynotes and full agenda for JS Interactive, taking place October 10 -12 in Vancouver BC, Canada. Experts from Alibaba Cloud, American Express, Best Buy, Disney, Google Cloud, IBM, Intel, Mozilla, Netflix, PBS, Walmart, Samsung, and Slack will present on how their organizations are adopting a range of JavaScript technologies, techniques, platforms and frameworks.

JS Interactive is a vendor-neutral event uniting the leading developers, end users, technical experts, maintainers and companies in the JavaScript ecosystem to further the education and advancement of Node.js and JavaScript. The program covers a broad spectrum of JavaScript ecosystem technologies, concepts and applications trends including server-side JavaScript, IoT, internationalization, accessibility, progressive web apps, serverless, voice-based apps, the offline-first approach, and much more. Registerfor JS Interactive by July 20 to save up to $549 USD. The full JS Interactive program can be viewed here.

“JS Interactive is one of the must-attend conferences for JavaScript developers,” said Sarah Novotny, Head of Open Source Strategy for Google Cloud Platform, Google. “The conference not only focuses on future trends related to this vast ecosystem, but also provides best practices for addressing common needs of the enterprise from security to performance.”

“JS Interactive brings both community and enterprise leaders under one roof to tap into the wealth of creativity and innovation within the ecosystem,” said Kris Borchers, Executive Director of the JS Foundation. “JS Interactive fosters knowledge sharing and practical dialogue that is indispensable to individual developers and senior executives alike. The event also educates end users on how to best adopt JavaScript within their businesses.”

“This should be a great event for both core developers and end users of JavaScript technology,” said Todd Moore, VP Open Technology of IBM and Chairperson of the Node.js Foundation Board. “Couple this with the great venue that Vancouver is and this will be memorable. The line up of talks and the concentration of experts make this the JavaScript event for the year.”

The schedule will feature keynotes and sessions from leading open source technologists including:

  • Garth Henson, JavaScript Engineer and Software Architect, The Walt Disney Company, keynote on JavaScript enterprise adoption and use at Disney
  • Alex Grigoryan, Head of Engineering for the Online Grocery and Application Platform team, WalmartLabs keynote on contrasting two approaches to tech transformation
  • Alolita Sharma, Principal Technologist, Amazon Web Services, shares best practices on how to globalize your JavaScript and Node.js applications
  • Teri Chadbourne, Developer Advocate, IBM, presents on the Offline First approach to web development
  • Myles Borins, Developer Advocate, Google, discusses inconsistencies between ES Modules and Common.js and how the Node.js Project is addressing and reconciling the problem
  • Antoinette Janus, Software Engineer, PBS Kids, talks about bridging the gap between designer and developer in contemporary web trends and topics
  • Nara Kasbergen, Software Engineer, NPR, outlines building voice-based apps with Node.js
  • Jamund Ferguson, JS Architect, PayPal, shares best practices for debugging Node.js in production
  • Ipsha Bhidonia, Tech Speaker, Mozilla, discusses service workers and how to start developing progressive web applications
  • Kazuhito Yokoi, Researcher, Hitachi, presents on different tooling around Node-RED

Along with keynotes and panels, JS Interactive will host several workshops during the conference. Workshops include:

  • “An Introduction to Web Components and Polymer,” John Riviello, Distinguished Engineer and Chris Lorenzo, Distinguished Engineer, Comcast
  • “Master Serverless with JS Foundation Architect,” Brian LeRoux, CTO, Begin
  • “A New Way to Profile Asnc Activity in Node.js,” Mathias Buus, Open Source Developer, nearForm
  • “Reading the Repo: A Workshop on Clear, Effective Communication Techniques,” Jory Burson, COO, Bocoup
  • “Vue.js Vixens Workshop,” Jen Looper, Senior Developer Advocate, Progress
  • “Hands-On Introduction to Kubernetes and OpenShift for JavaScript Hackers,” Ryan Jarvinen, Developer Advocate, Red Hat

Join the conference on social by following our hashtag #jsinteractive.

Registration, Accommodations and Travel to the Venue

Register hereby July 20 to save up to $549USDon registration. Hotel room rate discounts are available here. Book early to secure a spot and receive the discounted rates. Flight discounts are also available with Air Canada and Delta, more on how to secure a discount here.

JS Interactive Diversity Scholarship

JS Interactive is awarding a few scholarships based on a combination of need and impact. The scholarship includes a conference pass, coach airfare and hotel accommodation for three nights. For eligibility and how to apply click here. All submissions are due by July 6.

Mark Hinkle on stage at Node.js Interactive in Vancouver, B.C.

On stage for the Node.js State of the Union at Node Interactive 2017 in Vancouver, B.C.

As we come into this year’s Node.js Interactive conference it’s a good time to reflect on the State of Node.js, and by any reasonable measure the state of Node.js is very strong. Every day there are more than 8.8 million Node instances online, that number has grown by 800,000 in the last nine months alone. Every week there are more than 3 billion downloads of npm packages. The number of Node.js contributors has grown from 1,100 contributors last year to more than 1,500 contributors today. To date there have been a total of 444 releases, and we have 39,672 stars on Github. This is an enviable position for any technology and a testament to the value of Node.js and the dedication of the Node.js community.  

Growth of Node.js From a User Perspective

We see incredible success with Node.js for front-end, back-end and full stack development. In this year’s Node.js User Survey we got incredible feedback and gained increased understanding of how Node.js is being used. We know that the the biggest use case for Node.js is back-end development, but users are also developing cross-platform and desktop applications, enabling IoT and even powering security apps. This week we are launching our annual survey again to identify trends and track our progress. I highly encourage you to take the survey and share your insights with the rest of the community.  

Node.js is also fortunate to be getting praise from several reputable third parties. The Battery Ventures Open Source Software Index (Boss Index), which ranks popular open source applications based on public interest, user activity, jobs impact and overall open source community impact has ranked Node.js the 4th most important open source project. Node.js is in good company as only Linux, Git and MySQL were ahead of Node.js; we beat out  well-established and impactful projects like Docker, Apache Hadoop and Spark.

The analyst community has taken note as well. Forrester published a brief earlier this year extolling, “Digital Transformation Using Node.js.” They said:

“The growth of Node.js within companies is a testament to the platform’s versatility. It is moving beyond being simply an application platform, and beginning to be used for rapid experimentation with corporate data, application modernization, and IoT solutions.”

We also are seeing success as one of the most highly trafficked websites on the Internet according to research done by W3Techs. Node.js’ success at Twitter, LinkedIn, The New York Times, Netflix, Paypal and Yahoo! has significantly helped lend credibility to the project.

Open Source: The Punk Rock of the 21st Century

When I speak to groups and talk about Node.js I usually start with a very technical definition of what Node.js is and does. I talk about how Node.js utilizes the Chrome V8 engine to execute JavaScript on the server. This is huge for extending the language of the browser to the server and providing a foundation for developing many new kinds of applications.  

For those uninitiated in JavaScript development, I sometimes get a blank stare. However, when I talk about the incredible list of companies that are using Node.js – Airbnb, Lowes, Twitter, LinkedIn – and many others they have heard of I start to peak their interest.

Once I have their attention I like to use the analogy that open source developers are the punk rockers of their generation, something I truly believe. I then explain the reasons why I see similarities between punk rock and open source, particularly Node.js:

….many bands self-produced recordings and distributed them through informal channels….technical accessibility and a DIY spirit are prized in punk rock…….Punk rock is meant to be our freedom. We’re meant to be able to do what we want to do…. The issue of authenticity is important in the punk subculture—the pejorative term “poseur” is applied to those who associate with punk and adopt its stylistic attributes but are deemed not to share or understand the underlying values and philosophy…. At the end of the 20th century, punk rock had been adopted by the mainstream, as pop punk and punk rock bands such as Green Day, the Offspring and Blink-182 brought the genre to widespread popularity.  Wikipedia – Punk Rock

Node.js developers share this same DIY spirit, authenticity, and passion for their work. That passion has made Node.js a success. The lack of formality and the ability to collaborate share and express themselves has enabled Node.js to grow.

And just like punk rock, Node.js has gone mainstream. A small group of developers and users has risen to a level that is enviable by many mainstream technologies. As Node.js moves forward, it’s important to improve while not losing the “indy spirit” that has made us successful. It’s also important to accept the responsibility that we have to keep Node.js sustainable for the millions of users who depend on our technology every day.

The Future of Node.js: Grow, Engage, Educate

So what happens when you have meteoric success like Node? Sometimes you hit speed bumps and reach impasses. You face new problems and you start to reevaluate how you do things so you can continue to flourish. As we move forward with Node.js we need to make sure that we are working on making sure Node.js is a sustainable technology that will continue to support the needs of our developers and end users.

This year’s Node.js 6 was the most popular release – our LTS releases are increasingly becoming the most popular downloads. This move to provide a stable trusted version is one of the steps on the path to encouraging more users to engage with Node.js. To that end, I am advocating a very broad set of initiatives going forward – grow, engage and educate.


Node.js’ growth has been fairytale-like. Usage of the project is amazing. However, for Node.js to continue to succeed there needs to be more growth. Not just in raw numbers but in new industries, companies and organizations, all of which help build a more diverse developer and user core with a broader perspective.

We need to continue to share our success through press and analysts, so more users can discover not only the value of Node.js, but also the best places to use Node.js. We need to help enable our users to evangelize the technology and provide a platform to grow, through publications like Node.js Collection and more.  


Going forward we need to continue to engage users not only in GitHub, but through other venues that facilitate communication, like meetups, blogs and larger events. We need to help broaden our ecosystem and maintain our relationships with other technologies like JavaScript frameworks, databases, load balancers and cloud providers.

We need to make sure we foster a strong relationship with the package ecosystem that we critically depend on. 4,800 npm packages are published every week. That’s one package every two minutes 24 hours a day providing an unbelievable number of options to extend Node.js for a variety of uses. We want to where appropriate have strong relationships with those developers to help ensure they have the security and support they need to be successful.

“The community of npm and Node.js developers is now larger than the population of New York City, and they download more than 500 packages of reusable code every second,” said CJ Silverio, Chief Technology Officer of npm, Inc., which hosts the npm Registry of JavaScript packages. “Companies of every size have invested in developing within this ecosystem because it’s robust, secure, and growing more powerful every day.”

Node.js is one the most used workloads on Google, Microsoft and Amazon’s clouds. Twilio’s latest serverless offering is written and developed on Node.js. Google’s Cloud Functions is written in JavaScript and executed in a standard Node.js runtime.

Node.js is the most popular language on Bluemix. The developer base is very comfortable getting started with Node, and all of the other languages that IBM supports for polyglot developers. “Our view of the world is that it’s all about APIs. How to discover and make use of them, whether human or machine readable,” said Todd Moore, VP of Open Source Technologies at IBM in an interview with The New Stack.

We should continue to build our relationships with these companies, share stories about how best to use Node.js within these different environments, and engage with new developers who are sprouting up around cloud-native applications and arm them with best practices around Node.js.


We need to continue to educate our potential users and developers. The Code & Learns and NodeSchools have been very successful. We also need to continue to reach out to potential users who aren’t familiar with or as comfortable with open source and help them get up to speed with the Node.js Community and how to contribute to the project.

One of our biggest initiatives is around certifications that will dovetail with organizations providing training. Certification is not education, but it should provide a benchmark for training organizations to shoot for.

Overall, Node.js is in a good place, but we can and will be better. We need to evaluate our systems and structures to make sure we are ready for the next 8 million Node.js instances and to help encourage a better more effective community and collaboration. Our future relies on our ability to adapt and nurture that success and drive toward a stronger ecosystem that involves more developers, solution providers and others who can continue the work that has been done to date.

The breadth of the The Linux Foundation (affectionately known as The LF) is often overlooked due to its eponymous name. However, what may not be apparent to the layman is that The LF is providing a true foundation for the next generation of Internet infrastructure by cultivating the biggest shared technology investment in history. The LF is so much more than Linux. Our work encompasses projects from security and IoT, to networking and cloud computing, and beyond.

One blockbuster example, Hyperledger, celebrates its one-year anniversary this month. This is the open source blockchain project on which a new ecosystem of projects and products will be built that reinvents commercial transactions on the Internet. Hyperledger is helping redefine the financial industry to reduce fraud and improve security through a blockchain shared ledger.

Let’s Encrypt is another LF project that’s bringing a level of security to the Internet that was previously out of reach by offering a free and open automated certificate authority. Furthermore, our Core Infrastructure Initiative provides a collaborative effort for key infrastructure that’s used throughout the network but needed more resources to be developed and maintained effectively. CII helps provide support for OpenSSH, OpenSSL and NTP (the Network Time Protocol that is used for updating virtually every server on the Internet).

With Cloud Foundry and Node.js, we are working to help enable digital transformation of IT infrastructure by providing frameworks for delivering cloud applications that scale and thrive under an open source development model. Increasingly, Linux Foundation projects are addressing needs throughout the application stack. Cloud Foundry, a container-based application platform, provides a way for developers to deploy applications while abstracting away some of the complexities of the underlying infrastructure. In essence they help application developers deploy cloud-native applications. Node.js is providing a massively scalable Javascript framework that makes it much easier to build server-side applications for the cloud.

The Cloud Native Computing Foundation (CNCF), an LF project that supports the key projects needed to build and scale modern distributed systems, has just acquired the rights to the Rethink DB source code. The project was licensed under the GNU Affero General Public License, Version 3 (AGPLv3), a strong copyleft license, which limited the willingness of some companies to use and contribute to the software. CNCF paid $25,000 to purchase the RethinkDB copyright and assets and has re-licensed the software under the ASLv2, one of the most popular permissive software licenses, which enables anyone to use the software for any purpose without complicated requirements. (See related blog post “Why CNCF Recommends ASLv2”.) RethinkDB joins CNCF’s solid stable of software built for the cloud including fluentd (data collection), Prometheus (monitoring), Kubernetes (container orchestration), and others.

And with the massive adoption of container technology (e.g. Docker, rkt) The Linux Foundation is providing an open governance structure for containers under the Open Container Initiative (OCI.) The OCI currently offers two specifications: the Runtime Specification (runtime-spec) and the Image Specification (image-spec). Such specs make it possible for companies to safely stake their products and services on container technologies by providing certainty that their applications can run across platforms. This is the foundation of a new container ecosystem.

Open Source Foundations Beyond Code

It wasn’t so long ago that we declared Linux to be the operating system of the cloud. Now a whole host of new cloud technologies are being built on that model of open source development (and run on top of Linux.) The Linux Foundation is not only providing the foundations for developing the code base of these technologies, but also the other mechanisms needed to foster collaboration, learning, and development.

We have launched a number of training courses, both free and paid, for those operators and developers learning to sharpen their skills. For example, we provide a free Introduction to Cloud Infrastructure Technologies course through edX. We have also created a Kubernetes Fundamentals course to help users validate and gain the skills needed to take advantage of what is becoming the most widely deployed container orchestration tool. We also fill the needs for skills training in open source software that we aren’t directly involved in, such as our OpenStack course that helps users prepare for the OpenStack certification.

Finally, our commitment to open source provides users the tools they need to appropriately consume, develop, and learn about open source. Our Open Source Summit events have multiple technology tracks, including cloud computing. And our CloudNativeCon and Kubecon series of events are the de facto place to learn about Kubernetes and how to build and use cloud native applications. We produce the events where users, developers and solution providers can come together to learn and collaborate on open cloud technologies.

In the end, what we are seeing is that technology is increasingly becoming open source and companies that originally develop software to scratch their own itch are finding much broader applications of those efforts. Savvy companies are taking their open source projects and mustering industry support around them. Pivotal did so with Cloud Foundry, Google’s done this with Kubernetes, and Joyent with Node.js.

The LF is a shepherd for valuable technologies that may need extra help to find success, such as RethinkDB, and we have stepped in to provide support around a project that was not prospering under a single entity. That support has to encompass a diverse ecosystem of users, developers, and solution providers which all collaborate to solve problems and improve the usability of these projects.

Through open collaboration we are creating a new generation of Internet infrastructure that will itself provide the foundation for companies and ecosystems to thrive well into the future.

Learn more about The Linux Foundation projects. Watch Jim Zemlin’s keynote talk at Open Source Leadership Summit 2017. Watch now!

This week in open source and Linux news, Steven J. Vaughan-NIchols challenges the critics of the new Linux Foundation-Microsoft membership news, Fedora 25 is easy for newbies to use, and more. Keep reading for all the latest top OSS news!

1) Steven J. Vaughan-Nichols challenges the Microsoft challengers.

Open Source Has Won, and Microsoft Has Surrendered– ComputerWorld


Fedora 25

Fedora 25 makes Linux easy for n00bs. Read what else Alex Campbell has to say about the distro in his article for PCWorld.

2) “The Fedora community created one of the smoothest Linux Installation experiences ever [with Fedora 25.]”

Fedora 25 Makes Linux Easy Enough for Anyone to Try– PCWorld

3) “Let’s take a look at how wrong I was,” says Bryan Lunduke about his 2016 predictions from last year. 

2016 Linux Predictions: Which Ones Came True?– NetworkWorld

4) “The Node.js Foundation announced major milestones toward allowing the solution to work in a wide variety of VMs at the Linux Foundation’s Node.js Interactive conference this week.”

Notes from Node.js Interactive– SDTimes

5) OpenDaylight Project’s Neela Jacques investigates vendors’ practice of “openwashing.”

Are We in a Golden Age of Open Source or Just Openwashing?– NetworkWorld

To increase developer support and diversity in the Node.js open source community, the Node.js Foundation earlier this year brought in Tracy Hinds to be its Education Community Manager. She is charged with creating a certification program for Node.js, increasing diversity, and improving project documentation, among other things.

“We are recognizing the very wide range of users the Node.js space has and trying to make sure they are all taken care of when it comes to learning Node.js,” Tracy says.


Tracy Hinds

Tracy Hinds, Education Community Manager at Node.js

Tracy has been involved in the community from early on and was a major player in helping to grow the Node.js community in Portland, Oregon, through meetups, an early NodeSchool, and NodeBots. She has organized or founded three conferences annually (CascadiaFest, EmpireJS, and EmpireNode) and is the founder and president of GatherScript, a non-profit that provides educational and financial advisement support for technical events.

“This is a really exciting time to get to support and grow all of the communities that have been contributing to Node.js all these years,” she says.

Here, Tracy tells us more about how she got started as a developer and with Node.js, her goals for the year as the new Node.js education community manager, and the best ways for new contributors to get involved in the project. Tell us a little bit about your background, how did you get introduced to development, then Node.js and then education?

Tracy Hinds: My prior work was in healthcare administration. It was a purpose-filled field, but that didn’t reduce how colleagues and I were constantly frustrated by all the technology challenges that came with the vertical. I was in the field when the industry was adopting electronic medical records. I found myself spending far too much of my day trying to teach my really savvy coworkers how to use really poorly designed software.

I decided that I wanted to start solving these problems instead of banging my head up against them, so I learned how to code. I was mainly self-taught and was first introduced to Python. At the time, I was living in Portland, OR and through connections that I made in the community learning Python, I got my first job programming professionally at Urban Airship.

I was hired as a junior engineer under the condition that I would learn JavaScript. Of course, like in many cases, JavaScript introduced me to Node.js. There was a small, but very enthusiastic Node.js community in Portland, OR, and I went to several of their meetups, spoke at a my first conference (NodePDX), and got involved with organizing various events and helping to build the community through seeing all these opportunities to help. As a developer that really learned on your own, what advice would you give others to get started with this?

​Tracy: Be patient.​ You’ll be exposed to so much information early on and you’ll be excited to be good at it. It’s so much information to take in and apply. Much of it takes time and experience to learn, not just theoretical readings.

There will be times where you’re feeling like you’re up against a brick wall. That’s okay! As a programmer, you’ll be paid to solve problems you very likely don’t know the answer to yet. You’ve been hired because you know how to approach the journey of finding a solution.

Find a community of people who encourage and support you, and you’ll be setting yourself up for success. No programmer is an island. OSS relies on a lot of wonderful people collaborating to make things work! How about landing that first job, what are some things that people should be aware of in trying to get a job as a developer that you wish you would have known or that you found really helpful?

Tracy: I’d had friends who were programmers and had insisted I’d make a great one time after time. With the help of so many communities, friends, and mentors, I learned how to program in Python and some basic web engineering. I was unbelievably fortunate through my networking to find a job that was willing to hire me as a junior and asked that I deep-dive into JavaScript as a primary language.  

It’s really important to introduce yourself to people, go to these meetups to try to learn more, but also show that you are open and persistent enough to never stop learning. Developers are problem solvers, so if you show that early on and have the added skill of being able to communicate well (and therefore collaborate), the better. Making those connections, showing that I could keep an open mind while also being a bit stubborn, and being willing to really immerse myself in the world of programming helped keep me on track from a big career switch. Let’s get back to Node.js, tell us a little bit about what you are doing for the Node.js Foundation?

Tracy: I was hired to be the education community manager at the Node.js Foundation. Essentially what I’m trying to do is create materials that will help introduce developers to Node.js (new developers and those that have been in the field for a long time), help ensure that education is embedded in the process of learning Node.js through documentation, and promote diversity in the community through education. What are your other goals in creating education opportunities for the Node.js community at large?

Tracy: I have three major goals this year, the first is how to create and provide a certification program for Node.js.

The second is to help build out the diversity of the Node.js community and I believe that education is the best way to do that. I’ve been trying to take a look at what workshops and in-person events exist that help create a supportive, inclusive learning environment so that I can assess how the Node Foundation can support future work. People getting to learn together form bonds and lets down barriers a little, enough so that they are open to making friends through the challenges they are facing. It’s easier to build camaraderie when you’re struggling with the same problem in a NodeSchool workshop or fixing a broken route in a NodeTogether class with a little help. These events draw much more diverse groups underrepresented communities, career transitioners, other language users because they create spaces that are hellbent on being forgiving, friendly places to learn.  

My third is to improve the documentation in Node.js to help facilitate learning. Currently, that means lots of discussions with different types of Node.js users on what it means to improve documentation. I wanted to encourage API docs improvements because they felt sparse. However, the more conversations I’ve had about docs in Node.js, the more I’m finding that our lack of other spoken languages being supported is a huge barrier for folks to level up or even step into Node.js. I can’t begin to imagine how difficult it must be having to translate the essential documentation I would need into the language I speak in order to write code. It’s an incredible barrier. There’s good work being done in our working groups for this, but there aren’t enough folks to support such a big challenge. We need to be smart about how we’d approach this. What are some interesting things you are finding in creating this certification program, why is it important?

Tracy: Certifications are extremely important to developers that have previous coding experience and are employed by companies who require it for hiring or promotions. When you look at some older technology languages, like Java, they have fairly deep certifications process and plans. Those that have experience with these languages have expectations to have something similar when they convert to newer platforms/languages like Node.js.

Certifications can also be useful for what we see often in the Node.js ecosystem smaller companies and consultancies. It could be an interesting space when a group of engineers can show that they have their certifications and establishes them as competent and potentially more competitive than another group that isn’t quite there yet.

We are having our first meetings with the newly formed Education Advisory Group, which will allow a good representation of perspectives from Node Core, Foundation members, NodeSchool, and the ecosystem to help form the scope of the certification. We’ll move forward with what we establish as tasks a competent Node.js engineer could complete. It’s definitely a work in progress and will take about 9 months to accomplish. We’re partnering with the Linux Foundation to build this out as an in-browser, 3rd-party proctored remote test. Any sources currently that you would recommend to those that are interested in getting started with Node.js or that might need to brush up their skills?

Tracy: First, Ashley Williams has created a really great opportunity to introduce folks to Node.js and development in general that do not have experience in this space at all. The series is called NodeTogether and for the most part they are held wherever we are having our Node.js Live events. She is looking for those that want to participate and mentors, so definitely worth checking out.

Jon Kuperman released, which is awesome for folks who like video learning. There’s about 6 courses that add up to a pretty great, free intro to Node.js.

Finally, NodeSchool is filled to the brim with free workshoppers that cover such an incredible variety of essential skills in Node.js. I recommend checking out one of the local events in your area where mentors will help you run through many of these modules, and the website has support for 20 different spoken languages! The NodeSchool community events are so warm and friendly, and the online repo with active organizers is very encouraging and helpful. You joined the Foundation a few months ago, what are some of the major roadblocks you’ve been able to overcome or key initiatives that you’ve been able to launch or are going to launch (fairly soon)?

Tracy: We are making strides towards unearthing a lot of the really incredible activity that’s been happening in different corners of the world in Node.js and making plans on how the Node.js Foundation can elevate those communities. My strength is in seeing good people doing awesome work and removing their roadblocks by helping with processes that might be standing in their way.

The certification planning is moving forward. The Education Advisory Group is meeting and will have big ideas for years to come. We are recognizing the very wide range of users the Node.js space has and trying to make sure they are all taken care of when it comes to learning Node.js, be it through turning over rocks to find out which problems we can rally to in Documentation or elevating programs that help build out inclusivity and diversity of perspectives in our language. This is a really exciting time to get to support and grow all of the communities that have been contributing to Node.js all these years.