As much as I dislike Windows, and even in Windows will prefer WSL... Windows development is still a thing and I try to be friendly to Windows developers as much as reasonable.
That's why Concurrently exists even if there's Bash on Mac, Linux, BSD, etc.
I stopped at the second question, which is just weird, and beyond that, the second question will never end the loop.
I'm not sure if this was AI generated, or what, but it's just incomplete or weird to say the least.
Definitely not a great article... as it is, the Unicode character and surrogate detection isn't great, and even then doesn't really work right with the regexp for non-unicode surrogates. The notation of byte length should probably be a blurb and jump right into the Unicode detection, surrogates being another, related issue, and even then, it's problematic at best.
Not to mention the benchmark at the end is kind of useless and doesn't include the Unicode aware methods. Also, no mention of UCS-16 vs UTF-8 or other Unicode demarkation with strings in JS.
Definitely click-bait.
No benchmarks for the Unicode methods, which I suspect would be the desired results... The format of the article seems to spend too much effort on getting the byte length of a string, which is not the characters in a string.
Wish theses were up on the YouTube channel... looks like the live streams are there, but separated videos would be nice. Hopefully TBD. I generally watch stuff like this in the Living Room via YT or other services.