Search results
Ryan Dahl (born 1981) is an American software engineer who is best known for creating the Node.js JavaScript runtime as well as the Deno JavaScript/TypeScript runtime.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window.
Feb 9, 2023 · A decade ago, Ryan Dahl changed how web development works. Now, he wants to do it again with his new company Deno.
Mar 19, 2024 · Ryan Dahl, creator of Node.js and Deno, tells us about his journey into software development and the creation of Node.js. He explains why he started Deno, a new JavaScript runtime. Ryan also introduces JSR, an alternative to NPM, and emphasizes the importance of security in the JavaScript ecosystem.
May 1, 2024 · Ryan Dahl keeps finding new approaches to familiar tech. More than once, he’s played a central role in the evolution of an existing ecosystem. Now he’s part of an effort to modernize the many modules of code that developers import into their projects every day.
Aug 31, 2017 · Ryan Dahl never actually liked javascript. It was just the language that was available. TJ has a company based on go, so he is obviously emotionally invested in it.
Sep 7, 2023 · It's the story of Ryan Dahl, the person behind Node.js and Deno. The mastermind behind the non-blocking asynchronous I/O model of Node.js - a radical approach at that time to process thousands of requests per second.
Deno was co-created by Ryan Dahl, who also created Node.js. Deno explicitly takes on the role of both runtime and package manager within a single executable, rather than requiring a separate package-management program.
Node.js was initially written by Ryan Dahl in 2009, about 13 years after the introduction of the first server-side JavaScript environment, Netscape's LiveWire Pro Web. The initial release supported only Linux and Mac OS X.
Feb 18, 2021 · Ryan Dahl is the creator of the Node.js and the Deno JavaScript and TypeScript runtime. He talks about the challenges and challenges in developing Deno. He also discusses how he would have changed his approach to Node.JS if he could travel back in time.
