Here I share in more detail about some of my professional experiences and topics I've been studying that I think are relevant to share with the world.
I always thought it was really cool when I visited a creative website and saw that little ball following the mouse with a smooth, fluid movement. It looks simple, but behind it there is a pretty interesting technical implementation. In this article, we will analyze a code where I implemented a Mouse Follower on my website using React/Next.js and Tailwind CSS, and understand how it works step by step.
Why would anyone choose to use UTF-16? If it has the complexity of surrogate pairs and isn't ASCII-compatible, why have companies like Microsoft, Oracle, and Mozilla adopted it as the standard for their platforms?
Let's uncover the inner workings of UTF-16. But before diving into the technical explanation, think with me: if you were to design a system to encode Unicode in 16 bits, what immediate challenge would you face?
Before diving into the technical details of UTF-16, we need to take a step back and understand the fundamental problem that Unicode solves.
Imagine trying to write an email in Portuguese, Chinese, and Arabic all at once, and then sending that message to someone on the other side of the world. It seems simple today, but a few decades ago, this would have been a technical nightmare.
