It seems when designing Unicode most energy went into emoji. And there was nothing left for fancy things like fixed-length string buffers. The only explaination why UTF8 Buffers aren't compatible with UTF16 Buffers... is a really strong emoji...
What I find surpring here is this being about DNS. Simple optimization should have been done maybe 1997. Letting it build up to 100 TB is noteworthy, but on the other hand for IT that's common. It's surprising but also totally expected...
It improved a lot and it is good. On Linux I think the default way to go is still Lazarus. But with Delphi you can buy more shiny polished things on top. So for commercial use Delphi is more relevant. And there are enough differences in compatibility, so you most likely don't want to deal with both at the same time.
You don't have to use their premium database components. Just use something else as client-library.
I'm also not a fan of yearly payments. But with a $1200 license you usually get access to all old versions - including Delphi 7. After Delphi 6/7 at least Version 11/12 were usable for 64-bit. So I think at least once every other decade it is ok to get a usable 64-bit version of Delphi.
I think learning how to set up a local AI now requires less time than learning about potential pitfalls of token-plans and processing payments in corporate environments.
It's not that billing is complicated, but learning to set up a local AI is a lot more useful and more rewarding.
In case there is a decent forum about tech somewhere in the Alibaba cloud, I'll be interested. HN has built a certain unhealthy bias in a lot of subjects. But so far other places haven't gained enough traction, yet.
Sounds like a decent challenge. Needs AI Translation built into the forum infrastructure... But I'd give it a try. Before there was AI, I chatted a few times successfully in Chinese only using some translation tools. Now with AI it should be even easier.
https://artoria2e5.github.io/XB18030/
It seems when designing Unicode most energy went into emoji. And there was nothing left for fancy things like fixed-length string buffers. The only explaination why UTF8 Buffers aren't compatible with UTF16 Buffers... is a really strong emoji...
reply