WebAssembly

As explained in the high-level goals, to achieve a Minimum Viable Product, the initial focus is on C/C++.

quake3 has been compiling c code into portable mods since 18 years ago. they could have just used that.

>>13

Little endian is far more intuitive in that for example a pointer to a larger integer will still be valid if used as a pointer to a smaller integer so long as the value is less than the max range of the smaller integer type. With big endian it just becomes zero.

So it's more intuitive because it makes more unintentional bugs? Big endian fails fast (https://en.wikipedia.org/wiki/Fail-fast). If you get all zeroes, you will know there's a problem. Little endian looks like it works until your value is too large. If you want to lose the most significant bits, it's just as easy to do it with big endian.

I feel that the number "1488" should actually be written "8841", because that's how we write words: the first letter comes first.

Do you pronounce that as "eight, eighty, four hundred, one thousand"?

If I want to make a word longer I can keep sticking letters to the end of it without changing the meaning of the preceding letters

You write and pronounce words with the most significant part first. Significant, significance, signify. That's big endian.