AKAshish Kumarinhelloashish.hashnode.dev00Tree Shaking and Code Splitting in JavaScript11h ago · 11 min read · A 2MB gzipped JavaScript bundle is ~7MB for V8 to parse and compile. On a mid-range Android at 3G, that is 12 seconds before a single interaction is possible. Bundle size is not an abstract metric — iJoin discussion
AKAshish Kumarinhelloashish.hashnode.dev00Web Workers in React: Heavy Work Off Main Thread2d ago · 11 min read · Heavy CPU work — parsing large binary files, sorting 50,000 records, running ML inference — belongs on a separate thread, not the main thread. The main thread has one job: keep the UI responsive. EverJoin discussion
AKAshish Kumarinhelloashish.hashnode.dev00DOM Performance on Mobile: Lab vs Real Device RealityMay 10 · 13 min read · Style recalculation on a page with 10,000 DOM nodes takes ~180ms on a budget Android — 10x the entire 16.6ms frame budget. The exact same scroll that is imperceptible on a developer MacBook drops 90% Join discussion
AKAshish Kumarinhelloashish.hashnode.dev00React Re-rendering: When and Why Component Trees UpdateMay 8 · 12 min read · Related: Long Tasks and Main Thread Blocking heavy React renders are one of the most common sources of Long Tasks. React's default re-render behavior is intentionally conservative: when a parent re-rJoin discussion
AKAshish Kumarinhelloashish.hashnode.dev00React.memo, useMemo, useCallback: When They Help vs HurtMay 6 · 10 min read · Most React memoization is premature. useMemo on every derived value, useCallback on every function, React.memo on every component — this pattern adds comparison overhead and memory cost on every rendeJoin discussion
