Question
What deeper point about String Immutability should a senior Java developer mention?
- At senior level, the right answer is that String Immutability exists mostly for historical syntax reasons.
- Immutability reduces defensive-copy pressure and prevents accidental cross-layer mutation, which is why String works so well as a shared value type.
- At senior level, the JVM removes the tradeoffs around String Immutability, so design choices barely matter.
- At senior level, any approach to String Immutability is equally correct if it compiles and passes a small test.
Hint
Look beyond syntax and explain the runtime, API, or design consequence.
Answer and rationale
Correct answer: B. Immutability reduces defensive-copy pressure and prevents accidental cross-layer mutation, which is why String works so well as a shared value type.
Immutability reduces defensive-copy pressure and prevents accidental cross-layer mutation, which is why String works so well as a shared value type. This is the kind of tradeoff-aware answer senior interviews usually expect.
Track: Java