为何采用replace+toUpperCase而非直接调用toUpperCase？后者是否为不良实践

Great question! Let's unpack this clearly:

First: Why might someone use the replace() approach? #

The example you shared makes both methods look identical, but the replace() + regex approach shines when you need granular control or extra logic alongside uppercasing:

• Target specific characters only: The regex /[a-z]+/g only matches ASCII lowercase letters. If you wanted to avoid converting non-ASCII lowercase characters (like é, ñ, or Unicode letters), you could adjust the regex (or use a stricter pattern). toUpperCase() will convert all Unicode-compliant lowercase characters automatically.
• Add custom logic during conversion: You can sneak in extra steps inside the replacement function—like logging, modifying the matched string further, or counting conversions:

  const s = 'Keep on Asking';
  const r = s.replace(/[a-z]+/g, function(match) {
    console.log(`Converting fragment: "${match}"`); // Log each conversion
    return match.toUpperCase();
  });
  

• Legacy habits or lack of awareness: Some developers might be more comfortable with regex string manipulation and not realize toUpperCase() is a simpler native alternative for full-string uppercasing.

Is using toUpperCase() a bad practice? #

Absolutely not! In fact, for your exact use case (converting an entire string to uppercase), toUpperCase() is the better choice:

• More readable: Anyone looking at your code will immediately understand you're converting the whole string to uppercase—no need to parse a regex or replacement function.
• Better performance: Native string methods like toUpperCase() are optimized by JavaScript engines, whereas regex matching + function calls add unnecessary overhead.
• Simpler: It's one concise line instead of multiple parts, reducing the chance of typos or regex mistakes.

Wrap-up #

The replace() method is a flexible tool for complex string transformations, but for straightforward full-string uppercasing, toUpperCase() is the optimal, clean, and efficient solution. No shame in using it—it's exactly what it's designed for!

内容的提问来源于stack exchange，提问作者Min