JavaScript · DOM · Senior · Comparison
When would you manipulate the DOM directly vs using a virtual DOM / declarative UI framework?
Short Interview Answer
Direct DOM suits small widgets and precise control; declarative frameworks scale complex stateful UIs with predictable updates at the cost of abstraction.
Detailed Explanation
Direct DOM is fine for progressive enhancement, embeds, and performance-critical tiny interactions. As UI state grows, manual DOM sync becomes error-prone (bugs, XSS via `innerHTML`, inconsistent updates). Frameworks reconcile state to UI, handle batching, and provide components. Trade-offs: bundle size, learning curve, escaping hatch needs (`ref`). Lead/senior answers discuss islands architecture, migrating legacy jQuery incrementally, and measuring whether VDOM overhead matters for the use case.
Interview Tip
Avoid religious answers — pick based on complexity and team.
Common Mistake
Claiming virtual DOM is always faster than direct DOM.