History of Node.js

CHINTAMANI PALA — Sat, 21 Sep 2024 14:26:57 +0000

Today, I’m excited to share what I’ve learned about the history of Node.js from NamasteDev.com Special thanks to Akshay Saini 🚀 for breaking it down in Namaste NodeJS - Episode 1.
I took a deep dive into how Node.js revolutionized web development, and here are some fascinating highlights from its journey! 🌐

🔍 The Journey of Node.js:

📅 2009:

Ryan Dahl created Node.js to overcome the limitations of the blocking Apache HTTP server. It was first built using Firefox’s SpiderMonkey engine, but within two days, Ryan switched to Chrome’s V8 engine!
Node.js made it possible to run JavaScript outside the browser, featuring event-driven architecture and asynchronous I/O, making it highly efficient. Fun fact: Ryan originally named it Web.js, as it was designed for server creation.
Around the same time, Joyent, a company working on non-blocking servers, noticed Ryan’s work and funded further Node.js development.

📅 2010:

npm (Node Package Manager) was introduced by Isaac Z. Schlueter (a Joyent employee), creating a registry for managing packages.

📅 2011:

Microsoft collaborated with Joyent to make Node.js compatible with Windows, as it was initially built for macOS and Linux.

📅 2012:

By 2012, Ryan Dahl stepped away from Node.js, and Isaac Z. Schlueter, creator of npm, took over as the leader of Node.js.

📅 2014:

With Node.js development slowing down, Fedor Indutny forked the project and created io.js. In 2015, the two projects merged, forming the Node.js Foundation.

📅 2019:

In 2019, the JavaScript Foundation and Node.js Foundation merged and developed the OpenJS Foundation, uniting the broader JavaScript ecosystem.

✨ Key Features of Node.js:

Cross-platform and open-source, running on Windows, Linux, macOS, and more.
Enables JavaScript to run outside the browser.
Event-driven architecture with asynchronous I/O for improved efficiency.
Single language (JavaScript) for both client and server development. 🎯
Supported by a massive open-source community! 🤝

Follow me on linked: https://www.linkedin.com/in/chintamani-pala/

Node.js has had an incredible journey, and learning about it has inspired me to explore its potential even further! 💡

What is the difference between Library and Framework

CHINTAMANI PALA — Fri, 21 Jun 2024 20:04:21 +0000

While the terms "framework" and "library" are usually used interchangeably in software development, they relate to two concepts that serve different purposes, with distinctly different implications for their usage in a project. Here are the major differences:

Framework

Inversion of Control :
Definition: A framework dictates the structure and flow of an application. It calls the user-written individual code rather than the reverse.
Example: When using a framework, you normally follow its conventions and integrate your code into the lifecycle of the framework. Suppose you were writing a web application with Django or Ruby on Rails. You would define classes for models, views, and controllers in a way that the framework prescribes, and then the framework is responsible for how all of the pieces interact.
Structure and Convention :
Definition: Guidance in the form of predefined structures for your application, together with best practices, design patterns, and conventions.
For example, it is the Angular framework that gives guidance regarding how to structure your code with modules, components, and services. This helps in keeping the uniformity and makes the application more scalable.
Fully Functional :
Definition: More often, frameworks host a wide extent of built-in functionalities covering all aspects of application development, from database handling to user authentication.
An example would be that Spring Framework for Java provides embeddable features for web, security, and database interaction. This means you won't need to integrate various libraries to a greater extent. In this regard, a library is defined as a collection of functions or class libraries that you can call at will to perform certain tasks. You are in control of when and how to use it.
Example: If you are using a library, you would write the main flow of your application and call library functions as needed. In fact, you call utility functions inline in your code in many cases when you use Lodash for JavaScript.
Focused Functionality :
Definition: Almost all libraries are focused on narrow ranges of functionality. Thus, they can provide tools to help you do certain specific things:.
Example: React, a JavaScript library to build user interfaces, is only concerned with rendering UI components. It enforces no application architecture or handles any other concerns like routing or state management—unless you include other libraries like React Router or Redux, that is.
Loose Coupling :
Definition: It refers to when libraries, in their use, are utilised independently of an application and thus loosely coupled with it. They allow the use of multiple libraries if need be.
An example of this might be that a Node.js application could have Express for routing, Mongoose for MongoDB, and Passport for authentication. All these have some form of specified role, and none operate based on strict enforcement of structure. Summary Framework: It guides the general structure and flow and enforces conventions generally, including broad comprehensive functionality. You plug your code into the framework.
Library: It provides certain functionality, called directly from your code, which enables more control over the structure and flow of applications.

Forem: CHINTAMANI PALA

History of Node.js

🔍 The Journey of Node.js:

✨ Key Features of Node.js:

What is the difference between Library and Framework

Framework