title: Is it better to use Reflect.defineProperty instead of Object.defineProperty?
body: <p>Using eslint with React configurations I get an <strong>error</strong> when using <code>Object.defineProperty</code>. The error says:</p>
  
  <blockquote>
    <p>Avoid using <code>Object.defineProperty</code>, instead use <code>Reflect.defineProperty</code>. (prefer-reflect)</p>
  </blockquote>
  
  <p>On the eslint <a href="https://eslint.org/docs/rules/prefer-reflect" rel="noreferrer">documentation of prefer-reflect</a> they say it's deprecated, the reason being:</p>
  
  <blockquote>
    <p>The original intent of this rule now seems misguided as we have come to understand that <code>Reflect</code> methods are not actually intended to replace the <code>Object</code> counterparts the rule suggests, but rather exist as low-level primitives to be used with proxies in order to replicate the default behavior of various previously existing functionality.</p>
  </blockquote>
  
  <p>Then my question is: is there any advantage in using <code>Reflect.defineProperty</code> instead of <code>Object.defineProperty</code>?</p>