Run results for: charCodeAt vs codePointAt actually using unicode chars

Run details:

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 Edg/120.0.0.0

Browser: Chrome 120

Operating system: Windows

Device Platform: Desktop

Date tested: 2 years ago

charCodeAt

22.3M/s

codePointAt

15.6M/s

View exact numbers

Test name	Executions per second
✓ charCodeAt	22,315,252 Ops/sec
codePointAt	15,565,286 Ops/sec

Script Preparation code:

var str = "some str😀ing heresome string he😀resome string heresome st😀ring heresome str😀ing heresome 😀string heresome string heres😀ome string heresome string heresome stri😀g heresome string heresome string heresome str😀ing heresome string heresome string heresome string her😀😀😀😀esome string heresome string here😀some string here"

Tests:

charCodeAt
str.charCodeAt(20)
codePointAt
str.codePointAt(20)