JavaScript if...else Statement: Conditional Logic for Real-World Applications

You know how JavaScript performs one function at a time and it becomes time consuming when a function takes too long to complete? This is because Js is a single threaded language and this behavior is called as synchronous. It can perform one task at a time which blocks other code. This can be solved by using Asynchronous functions (non-blocking way). JavaScript can execute code in two different ways: Synchronous (Blocking) Code runs line by line Each task waits for the previous one to finish If one task is slow, everything else pauses Think of it as a single-lane road. Asynchronous (Non-blocking) Time-consuming tasks run in the background JavaScript continues executing other code Once the task is done, the result is handled. In the next post I will tell how asnyc functions work. See you later. Cheers!! #JavaScript #WebDevelopment #MERN #AsyncJS #LearningInPublic

✨ 𝗗𝗮𝘆 𝟮𝟮 𝗼𝗳 𝗠𝘆 𝗝𝗮𝘃𝗮𝗦𝗰𝗿𝗶𝗽𝘁 𝗝𝗼𝘂𝗿𝗻𝗲𝘆 🚀 (𝗙𝗶𝗻𝗮𝗹 𝗗𝗮𝘆 𝗼𝗳 𝗝𝗦 𝗙𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀) Today I learned about the 𝘁𝗵𝗶𝘀 𝗸𝗲𝘆𝘄𝗼𝗿𝗱 and how its value changes in different scenarios in JavaScript. I explored how 𝘁𝗵𝗶𝘀 behaves in: 🔹 Global context 🔹 Regular functions 🔹 Object methods 🔹 Arrow functions 🔹 Constructor functions / classes I also learned how to control 𝘁𝗵𝗶𝘀 using 𝗰𝗮𝗹𝗹(), 𝗮𝗽𝗽𝗹𝘆(), 𝗮𝗻𝗱 𝗯𝗶𝗻𝗱(). Another important concept was understanding 𝗦𝘁𝗿𝗶𝗰𝘁 𝗠𝗼𝗱𝗲 𝘃𝘀 𝗡𝗼𝗻-𝗦𝘁𝗿𝗶𝗰𝘁 𝗠𝗼𝗱𝗲. In strict mode ("𝘂𝘀𝗲 𝘀𝘁𝗿𝗶𝗰𝘁"), JavaScript enforces stricter rules and prevents some common mistakes. For example, inside a regular function this becomes undefined instead of the global object, making behavior more predictable. Finishing these JavaScript fundamentals feels great. Now it’s time to move forward and build more complex projects! 💪 #JavaScript #100DaysOfCode #WebDevelopment #LearningJourney #FrontendDevelopment

I learned about default parameters in JavaScript. When we assign a value using = in a function parameter, that value works as a default. If no argument is passed, instead of getting undefined, the default value is used. This works in regular functions and arrow functions, and it makes the code safer and cleaner. Small concept, but very useful in real projects. #JavaScript #ES6 #Functions #LearningJourney #WebDevelopment

JAVASCRIPT NOTES — PART 4 (Core Concepts) This is where JavaScript stops feeling simple. Understanding execution context, closures, and prototypes changes how you read and write code. This post covers: • How execution context actually works • Memory creation & scope chain • Closures and preserved state • Prototype chain & inheritance • Constructor functions vs classes Once these are clear, the language becomes predictable instead of confusing. 📌 Save this for deep revision. #JavaScript #FrontendDeveloper #WebDevelopment #InterviewPrep #LearningInPublic #Closures #Prototypes #Consistency

Still creating promises the old messy way in JavaScript? Many developers still write complicated promise setups that are hard to read and maintain. Modern JavaScript now offers a cleaner approach with Promise.withResolvers(), making async control more structured and easier to manage. Small improvements like this can make your code much cleaner and more readable. Follow for more modern JavaScript dev tips. #JavaScript #WebDevelopment #CodingTips #Developers #ModernJavaScript #FrontendDevelopment #Syncfusion

A small but common mistake when working with asynchronous JavaScript: forgetting await. Everything in the code can look correct, the function is async, the logic makes sense, but without await, the result you expect never arrives when you need it. It’s a simple oversight, but it can cause confusing behavior when working with APIs or database calls. Sometimes the difference between a bug and a working feature is just one keyword. #JavaScript #AsyncAwait #SoftwareDevelopment #WebDevelopment #Debugging #DeveloperExperience

JavaScript is single-threaded, but asynchronous behavior is managed by the Event Loop. 👉 Execution Order: 1️⃣ Call Stack – Executes synchronous code 2️⃣ Microtask Queue – Promises (High Priority) 3️⃣ Macrotask Queue – setTimeout, setInterval, DOM events (Low Priority) The Event Loop processes all microtasks before executing the next macrotask. That’s why Promise callbacks run before setTimeout — even with 0ms delay. Understanding this mechanism is crucial for writing efficient and non-blocking JavaScript applications. #JavaScript #EventLoop #AsyncJS #FrontendDeveloper #WebDevelopment 🚀

There is no JSX in Granular. No TSX. No template DSL. No special syntax that needs a compiler to understand. DOM elements are JavaScript functions: Div, H2, P, Button - you compose them just like you compose any other function. Props and children can appear in any order, any number of times. They are merged automatically. This is more flexible than JSX and requires zero transpilation. Your IDE gives you full autocomplete and type checking out of the box. No special plugins, no language server extensions, no build tool configuration. JavaScript is the template language. The function call is the component. npm create @granularjs/app my-app #javascript #frontend #webdev #dx #opensource

JAVASCRIPT NOTES — PART 3 (Async JavaScript) Synchronous code is easy to follow. Asynchronous code is where real confusion begins. This post covers: • Callbacks and why they became messy • Promises and their states • async / await for cleaner flow • Error handling with try–catch • The Event Loop and execution order • Microtasks vs callback queue Understanding async JavaScript isn’t about memorizing syntax — it’s about knowing when and why code executes. If the event loop ever felt confusing, this one is for revision. #JavaScript #WebDevelopment #FrontendDeveloper #LearningInPublic #InterviewPrep #AsyncJavaScript #Consistency

🚀 JavaScript Promise Insight: When Does the Promise Executor Run? 🧠 A common misconception in JavaScript is that the callback function you pass to a Promise constructor runs asynchronously or gets queued as a microtask. Spoiler alert: It doesn’t! 🔍 Let’s clarify: What’s happening here? The executor function you pass to new Promise() runs immediately, on the spot. That means console.log('2') outputs before anything else. Calling resolve() inside the executor also executes synchronously—no microtasks involved yet. The asynchronous part happens only when you attach .then() handlers. These callbacks get queued in the microtask queue and run after the current call stack clears. ✨ Knowing this helps you anticipate the order of execution in your async code and avoid subtle bugs. #JavaScript #AsyncProgramming #Promises #WebDevelopment #CodingTips #JavaScriptTips