By @addaleax MongoDB When server-side JavaScript crashes, the problem may lie beyond JS. This talk shows how native debuggers and tracing tools help investigate memory leaks and crashes across the boundary between JavaScript and C/C++. tickets available: https://lnkd.in/eR2QazBH #javascript #nodejs #debugging #perfomance
Debugging JavaScript Crashes with Native Tools
More Relevant Posts
-
Behind the Screen – #35 Do you know? #Browsers don’t understand your modern JavaScript directly. Features like: 👉 JSX (in React) 👉 ES6+ syntax 👉 TypeScript need to be converted into browser-friendly code. This is where #compilers come in. Tools like #Babel or #TypeScript compiler: 👉 Read your source code 👉 Transform it into simpler JavaScript 👉 Ensure compatibility across browsers For example: JSX → converted into plain #JavaScript Modern syntax → converted into older supported versions That’s why your code works even in different environments. You write modern code. The compiler makes it runnable. 🔥 Compilers bridge the gap between developer-friendly code and machine-friendly execution. #javascript #reactjs #compiler #webdevelopment #techfacts
To view or add a comment, sign in
-
A single search bar can accidentally send dozens of API requests. Day-12 of building in public I recently learned how a small JavaScript technique called debouncing helps solve this. Imagine a user typing in a search field. Without debouncing, every keystroke can trigger a request to the server. If someone types quickly, the application might send many unnecessary API calls. Debouncing introduces a small delay before executing the function. If the user keeps typing, the timer resets — and the function only runs after the user stops typing. This means instead of multiple requests, the server receives only one meaningful request. A simple concept, but it can significantly improve performance and make applications more efficient. Sometimes small techniques make a big difference in how applications behave. #javascript #webdevelopment #frontenddevelopment #learninginpublic #SheryiansCodingSchool
To view or add a comment, sign in
-
-
🚀 What I Learned Today: Node.js Internals • Node.js runs JavaScript on a single main thread • Top-level code executes first before the event loop starts • Import statements load during initialization • Event Loop manages asynchronous operations Event Loop Phases: • Timers → setTimeout() / setInterval() • I/O Polling → file system & network operations • Check → setImmediate() (Node.js specific) • Close Callbacks → cleanup tasks • Node.js uses a libuv worker thread pool (default: 4 threads) • Thread pool size can be changed using process.env.UV_THREADPOOL_SIZE https://lnkd.in/gwFG5WVW thank you Piyush Garg sir Hitesh Choudhary sir Akash Kadlag sir #chaiaurcode #NodeJS #JavaScript #Backend #EventLoop
To view or add a comment, sign in
-
-
🚨 JavaScript Tricky Question #3 (Advanced) What will be the output? 🤯 Promise.resolve() .then(() => { console.log("A"); throw new Error("Error!"); }) .catch(() => { console.log("B"); }) .then(() => { console.log("C"); }); Think carefully (this is tricky) 💬 Comment your answer 👇 🔁 Follow for daily advanced JS questions #javascriptdeveloper #mernstackdeveloper #frontendinterview #javascriptquestions #webdevelopmenttips #learnjavascript #jsconcepts #asyncjavascript #developersindia #codinginterview #softwaredeveloperlife #nodejsdeveloper #reactdeveloper #techcareers
To view or add a comment, sign in
-
Just published a new article: Node.js: The New Era of JavaScript Runtime Environments. In this article, I cover: What a browser receives from a server (HTML, CSS, JavaScript) Why JavaScript traditionally ran only in the browser How Node.js made it possible to run JavaScript on the server The high-level role of V8 and system APIs in Node.js #nodejs #javascript #webdevelopment #backend #programming
To view or add a comment, sign in
-
The Silent Killer in Your JavaScript Code: Unpredictable Date Parsing 🚨 Many developers don't realize how dangerous JavaScript's date type conversion can be. One wrong input, and your entire application could be generating phantom dates or throwing cryptic errors. This isn't just a minor inconvenience - it's a potential security and reliability nightmare that can slip past code reviews undetected. Understanding these parsing quirks isn't optional; it's essential for writing robust web applications. Have you ever encountered a date-related bug that drove you crazy?
To view or add a comment, sign in
-
-
𝗪𝗵𝘆 𝗬𝗼𝘂 𝗦𝗵𝗼𝘂𝗹𝗱 𝗦𝘁𝗼𝗽 𝗠𝘂𝘁𝗮𝘁𝗶𝗻𝗴 𝗔𝗿𝗿𝗮𝘆𝘀 𝗶𝗻 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 (𝘚𝘦𝘳𝘪𝘰𝘶𝘴𝘭𝘺) 🧐 If you’ve been writing JavaScript for a while, you’ve probably spent hours debugging a feature that simply refused to update on the screen, only to realize the data had changed, but the app didn’t know it. #javascript #WebDevelopment #FullStackDeveloper
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
-
🚀 Concurrency vs. Parallelism in JavaScript: easier than it seems (Javascript) Many developers confuse these concepts, but they’re simple once you see them in JS: * Concurrency: handling multiple tasks at the same time, but not necessarily simultaneously. In JS, this happens thanks to the event loop. * Parallelism: executing multiple tasks at the exact same time. In JS, we can do this with Web Workers (browser) or worker threads (Node.js) ⚠️ Tip: Parallelism is powerful, but don’t overuse it. Spawning too many threads or workers can overwhelm your CPU, memory, or event loop, making your system slower instead of faster. 💡 Takeaway: Concurrency ≠ Parallelism. Understand the event loop and workers to write efficient, scalable JS code, but balance parallel tasks wisely.
To view or add a comment, sign in
-
-
Today Class was on Internals of Node.js! Understood how Node.js runs on a single main thread, uses the event loop to handle async tasks, and a thread pool (default 4 threads) for heavy operations. Also learned how phases like I/O polling, expired callbacks, and setImmediate work behind the scenes. Really interesting to see how Node.js executes code internally. #NodeJS #NodeJSInternals #JavaScript #EventLoop #ChaiCohort26 #Chaicode Hitesh Choudhary Chai Code #piyushgarg Anirudh Jwala Akash Kadlag Jay Kadlag JavaScript
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