Romaji to Kana Converter: Astro — Chapter 4, Exercise 3
=====================================================================

TASK
In your own words, explain why this page's on-input conversion needs
no debouncing at all, and name specifically what would have to change
about where the conversion logic runs for debouncing to genuinely
become necessary.

SOLUTION

Debouncing exists to reduce how often an expensive or rate-limited
operation runs -- typically by waiting for a short pause in a rapid
sequence of triggers before actually doing the work, so ten keystrokes
typed in quick succession result in one real operation instead of ten.
It's a genuinely useful technique specifically when each individual
call is costly: a network request has real latency and consumes a
real server resource on the other end, so firing one per keystroke
could mean dozens of wasted, overlapping requests for a single word.

convert() has neither of those properties. It's a synchronous,
in-memory function running entirely inside the same browser tab the
user is typing in -- there's no network round trip to wait on, no
server-side resource being consumed, and no meaningful cost difference
between calling it once and calling it fifty times in a row. Even a
very fast typist firing an input event every few milliseconds costs
this page nothing worth optimizing away, since the entire operation
completes well within a single frame.

What would actually make debouncing necessary is exactly the change
Chapter 5 explores directly: moving convert() off this page and behind
a real network call -- an Astro server endpoint, a fetch to some other
service, anything that has to leave the browser and come back. The
moment conversion depends on a round trip with real latency and a real
server picking up the request, converting on every single keystroke
stops being free and starts being a real, measurable cost -- at which
point debouncing (or some other request-limiting strategy) becomes a
genuine, worthwhile tradeoff rather than unnecessary complexity.

WHY THIS WORKS AS AN ANSWER
----------------------------
It names the real, general reason debouncing exists (reducing the
frequency of costly operations) and then applies that reasoning
correctly to this specific function -- recognizing that convert()
currently has no real cost to reduce -- before naming the precise
structural change (moving the call behind a network request) that
would introduce one, tying directly forward to what Chapter 5 is
actually going to build and measure.