> Microsoft are free to change the Native API at will,...
But they won't, because if there is one thing that Microsoft has always been extremely good at and cared for is backward compatibility. And changing Native API will break a ton of existing software, because even though undocumented it is very widely used.
They depricate some methods (very rarely and reasonably) and add new enums or struct versions to existing ones, but never change existing semantics, leave alone method signatures. As I said elsewhere, I invite you to find examples of actually destructive Native API changes.
Some laptops had them, and came with IR remotes. Some of the marketing was around using those laptops as "media centres", and you could control them from the sofa while it was plugged into a TV.
To be more specific (see my general comment), I’ve used the language in two open-source projects: 1) a chromosome conformation reconstruction tool, and 2) a fast neural network generator (back end). Re Project 2: I’m also planning to embed the language into results webpages served from the NN generator website.
Yup! A fairly simple deterministic RNG such that it can be generated both client and server side. This strategy greatly reduces the burden of transmitting all the letters as you scroll around, only needing the subset of found words
If in doubt, try and find examples of its breakage, semantic changes, etc.
reply