𝘧𝘪𝘯𝘢𝘭𝘭𝘺 𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘰𝘰𝘥 𝘩𝘰𝘸 𝙉𝙤𝙙𝙚.𝙟𝙨 𝘸𝘰𝘳𝘬𝘴 𝘣𝘦𝘩𝘪𝘯𝘥 𝘵𝘩𝘦 𝘴𝘤𝘦𝘯𝘦𝘴, 𝘢𝘯𝘥 𝘪𝘵 𝘤𝘩𝘢𝘯𝘨𝘦𝘥 𝘵𝘩𝘦 𝘸𝘢𝘺 𝘐 𝘴𝘦𝘦 𝘵𝘩𝘦 𝙟𝙖𝙫𝙖𝙨𝙘𝙧𝙞𝙥𝙩 𝙧𝙪𝙣𝙩𝙞𝙢𝙚. 🚀 Day 19 – 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠 𝐍𝐨𝐝𝐞.𝐣𝐬 𝐈𝐧𝐭𝐞𝐫𝐧𝐚𝐥𝐬 𝐰𝐢𝐭𝐡 𝐏𝐢𝐲𝐮𝐬𝐡 𝐆𝐚𝐫𝐠 Today I learned: 𝘝8 Engine compiles JavaScript into machine code. 𝘊++ bindings connect JavaScript with system-level operations. 𝗹𝗶𝗯𝘂𝘃manages asynchronous I/O, event loop, and thread pool. The Event Loop keeps 𝙉𝙤𝙙𝙚.𝙟𝙨 non-blocking. The Thread Pool handles heavy tasks like file system, DNS, and crypto. Key takeaway: 𝘕𝘰𝘥𝘦.𝘫𝘴 = 𝘝8 + 𝘊++ 𝘉𝘪𝘯𝘥𝘪𝘯𝘨𝘴 + 𝘭𝘪𝘣𝘶𝘷 + 𝘌𝘷𝘦𝘯𝘵 𝘓𝘰𝘰𝘱 + 𝘛𝘩𝘳𝘦𝘢𝘥 𝘗𝘰𝘰𝘭⚡ #WebDev #nodeJS #Javascript #ChaiAurCode
Learning Node.js Internals with V8 Engine and C++ Bindings
More Relevant Posts
-
💡 𝗧𝗶𝗽 𝗼𝗳 𝘁𝗵𝗲 𝗗𝗮𝘆 — 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗗𝗶𝗱 𝘆𝗼𝘂 𝗸𝗻𝗼𝘄? "Object.freeze()" makes an object 𝗶𝗺𝗺𝘂𝘁𝗮𝗯𝗹𝗲 — but only at the top level. That means: - You 𝗰𝗮𝗻𝗻𝗼𝘁 𝗮𝗱𝗱, 𝗿𝗲𝗺𝗼𝘃𝗲, 𝗼𝗿 𝗰𝗵𝗮𝗻𝗴𝗲 properties on the frozen object - But 𝗻𝗲𝘀𝘁𝗲𝗱 𝗼𝗯𝗷𝗲𝗰𝘁𝘀 𝗰𝗮𝗻 𝘀𝘁𝗶𝗹𝗹 𝗯𝗲 𝗺𝗼𝗱𝗶𝗳𝗶𝗲𝗱 🔧 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁: If you need full immutability, you’ll need a 𝗱𝗲𝗲𝗽 𝗳𝗿𝗲𝗲𝘇𝗲 (or use libraries like Immer). Shallow vs deep immutability — a small detail that can cause big bugs. #JavaScript #FrontendDevelopment #WebDevelopment #SoftwareEngineering #CodingTips #CleanCode #BestPractices #FullstackDeveloper
To view or add a comment, sign in
-
-
🚀 Day 955 of #1000DaysOfCode ✨ How JavaScript Event Loop Works Behind the Curtains JavaScript looks simple on the surface — but under the hood, a lot is happening to make async code work smoothly. In today’s post, I’ve explained how the JavaScript Event Loop actually works behind the scenes, so you can understand how tasks are executed, queued, and prioritized. From the call stack to the callback queue and microtask queue, this concept explains why some functions run before others — even when the code looks sequential. Understanding the event loop helps you debug tricky async issues, avoid unexpected behavior, and write more predictable code. If you’re working with promises, async/await, or APIs, this is one of those concepts you must truly understand. 👇 What part of the event loop confuses you the most — call stack, microtasks, or callbacks? #Day955 #learningoftheday #1000daysofcodingchallenge #FrontendDevelopment #WebDevelopment #JavaScript #React #CodingCommunity #AsyncJavaScript
To view or add a comment, sign in
-
🚀 Day 944 of #1000DaysOfCode ✨ Understanding Temporal Dead Zone in JavaScript JavaScript can sometimes behave in unexpected ways — especially when it comes to variable declarations. In today’s post, I’ve explained the concept of the Temporal Dead Zone (TDZ) in a simple and practical way, so you can understand why accessing variables before declaration can throw errors. The TDZ is the time between when a variable is hoisted and when it is actually initialized. This is why variables declared with `let` and `const` behave differently compared to `var`. Understanding this concept helps you avoid tricky bugs and write more predictable and cleaner code. If you’re working with modern JavaScript, knowing how TDZ works is essential for debugging and writing reliable applications. 👇 Have you ever faced a TDZ-related error without knowing the reason? #Day944 #learningoftheday #1000daysofcodingchallenge #FrontendDevelopment #WebDevelopment #JavaScript #React #Next #CodingCommunity #AsyncJavaScript
To view or add a comment, sign in
-
🚀 Promises in JavaScript — Simplified Handling asynchronous operations in JavaScript can get messy… especially with callback hell. That’s where Promises come in. 👉 A Promise is an object that represents a future value — something that will be available after an async operation completes. It has 3 states: 1️⃣ Pending → Initial state (waiting) 2️⃣ Fulfilled → Operation successful 3️⃣ Rejected → Operation failed 💡 Promises make async code cleaner, readable, and easier to manage compared to callbacks. Mastering this is a must for every JavaScript developer 💯 #JavaScript #WebDevelopment #FrontendDevelopment #AsyncProgramming #Coding
To view or add a comment, sign in
-
-
Most people think they understand JavaScript classes. They don’t. Because JavaScript doesn’t even have real classes. What it actually has is prototypes — and classes are just syntactic sugar on top of them. Today in my T9 class, this completely changed how I look at JS: → Prototype-based inheritance (the actual mechanism) → Traditional vs Modern prototype handling → Constructor Functions (how things worked before classes) Then we moved to what most people are comfortable with: → Classes in JavaScript → constructor, extends, super, static → The 4 pillars of OOP: Encapsulation Inheritance Polymorphism Abstraction But here’s the uncomfortable truth: If you don’t understand prototypes, you don’t actually understand inheritance in JavaScript. You’re just memorizing syntax. That’s why debugging feels random. That’s why “this” behaves weird. That’s why things break in unexpected ways. Now it makes sense. Still early in the journey — but this was one of those “everything clicks” moments. Do you think JS should have stayed purely prototype-based, or are classes a good abstraction? #JavaScript #OOPS #WebDevelopment #LearningInPublic Thankyou Chai Aur Code Suraj Kumar Jha Sir Hitesh Choudhary Sir Piyush Garg Sir
To view or add a comment, sign in
-
-
Day 14 #100DaysOfCode 💻 Today I learned Promise & Async/Await in JavaScript. Promise helps handle asynchronous operations like API calls. Async/Await makes code cleaner and easier to read. Example: function getData() { return new Promise((resolve) => { setTimeout(() => { resolve("Data received"); }, 1000); }); } async function fetchData() { const result = await getData(); console.log(result); } fetchData(); Now I can handle async code without messy callbacks 🚀 #JavaScript #AsyncAwait #Promise #WebDevelopment #CodingJourney #Akbiplob
To view or add a comment, sign in
-
TypeScript 6.0 is your final warning TypeScript 6.0 has been released as the last version built on its JavaScript codebase, serving as a transition before TypeScript 7.0 introduces a Go-based compiler with native speed and multi-threaded type checking. Key changes include strict mode enabled by default, module defaulting to esnext, target floating to the current ES spec (es2025), and types defaulting to an empty array — a change that may break many projects but promises 20–50% speed improvements. New features include built-in Temporal API types and Map.getOrInsert support. Several legacy options like outFile, baseUrl, and AMD/UMD/SystemJS targets are deprecated or removed. The newsletter also covers pnpm 11 beta, Zero 1.0 stable release, a React useState closure gotcha, and various other JavaScript ecosystem links
To view or add a comment, sign in
-
-
hi connections Day 16 of 30: Implementing a Promise Time Limit! Moving deeper into the Asynchronous section of my 30 Days of JavaScript on LeetCode. Today was about adding a "safety net" to our code. 🛠️⏳ The Goal: Wrap an async function so that if it takes longer than a specified time t, it immediately fails with a "Time Limit Exceeded" error. The Lesson: I used Promise.race() to pit the actual function against a custom timeout promise. This pattern is crucial for building resilient systems. Whether it's a web crawler or a high-traffic API, you never want one slow request to block your entire event loop. Control the time, control the performance! 💻🔥 #JavaScript #WebDevelopment #CodingChallenge #LeetCode #Day16 #SoftwareEngineering #AsyncJS #PerformanceOptimization
To view or add a comment, sign in
-
-
🚀 JavaScript Fundamentals Series — Part 8 Objects are one of the most important concepts in JavaScript. Almost everything in JavaScript is built around objects. This guide covers: • What objects really are • Properties and methods • How JavaScript structures data • Why objects are everywhere in JS If you want to truly understand JavaScript, you must understand objects. Full guide 👇 https://lnkd.in/dGHh7weZ #javascript #coding #webdev
To view or add a comment, sign in
-
[Article] Ever wondered what actually #TypeScript do. It's not just adding types & stripping them away! It's a sophisticated 5-stage pipeline: 1️⃣ 𝐋𝐞𝐱𝐞𝐫: Turns raw code into meaning full "Tokens" 2️⃣ 𝐏𝐚𝐫𝐬𝐞𝐫: Organizes those tokens into an Abstract Syntax Tree (AST) 3️⃣ 𝐁𝐢𝐧𝐝𝐞𝐫: Creates Symbol Table to manage scopes 4️⃣ 𝐂𝐡𝐞𝐜𝐤𝐞𝐫 (𝐓𝐡𝐞 𝐁𝐫𝐚𝐢𝐧): This is where type validation and inference happens. 5️⃣ 𝐄𝐦𝐢𝐭𝐭𝐞𝐫 (𝐉𝐒): Transform TypeScript code into JavaScript code. Read TS internals:- https://lnkd.in/g7NMPD-9 Grateful to • Hitesh Choudhary • Piyush Garg • Akash Kadlag • Nikhil Rathore • Jay Kadlag • Anirudh Jwala • Suraj Kumar Jha • Chai Aur Code for the guidance. #TypeScript #SoftwareEngineering #WebDevelopment #JavaScript #Compiler #ProgrammingTips #StackAtlas #NodeJs #LearnInPublic #cohort26 #ChaiCode #ChaiAurCode
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development