KSKanishka Shashiinhtml-dev09.hashnode.dev·Jul 10 · 12 min readHow React Works Internally: Virtual DOM, Reconciliation, and RenderingIntroduction What actually happens when we call setState? You click a button. setCount(count + 1); The number on the screen changes instantly. But what happens behind the scenes? Does React rebuild 00
KSKanishka Shashiinhtml-dev09.hashnode.dev·Jul 10 · 11 min readKafka Explained Like You're 5: Events, Partitions, and Consumer GroupsIntroduction How does a large application process millions of events every day? Imagine a food delivery app during dinner time. Thousands of customers are placing orders, restaurants are accepting the11C
KSKanishka Shashiinnodej.hashnode.dev·Jul 10 · 11 min readReact Hooks Masterclass: useState, useEffect, and Custom HooksIntroduction How does React remember information between renders? Imagine clicking a button that increases a counter. The component function runs again after every click, yet React somehow remembers t00
KSKanishka Shashiinhtml-dev09.hashnode.dev·Jul 10 · 19 min readNext.js Explained: Why It Became the Default React FrameworkThe question that started it all If React is so popular, why was Next.js created? React solved a real problem: building complex, interactive user interfaces out of small, reusable, declarative compone00
KSKanishka Shashiinnodej.hashnode.dev·Jul 8 · 19 min readReact Fundamentals: Components, JSX, State, and Re-renderingThe question that started it all Why did developers create React when JavaScript already existed? JavaScript could already change a web page after it loaded — you could grab an element with document.g00
