Can you explain this or point me to the relevant documentation or code please?
1,162 karma · joined May 24, 2010
Can you explain this or point me to the relevant documentation or code please?
On the other hand, the reason I'm very skeptical about this story is this part: "Near the end there was reportedly a heavy shake and the cabin tilted sharply to one side. After further screams the video ended, Bild said."
The impact speed has been estimated at about 700 km/h, or about 200 metres per second. The fuselage of an A320 is 37 metres long. First impact to complete destruction would take about 1/10 of a second; the described sequence of events takes far too long to be plausible. (The only way it might work is if the first impact was on a wingtip.)
This seems to be basically just a chat server (with message attachments). The notebook style UI is cute but doesn't seem to mean anything. Is there anything here I couldn't do on Skype?
What platforms does this support? There's a picture of a laptop, a tablet, and a phone. They all look vaguely like Apple products, so maybe this is Mac/iOS only, or maybe that's just the icons you happened to have on hand. If it is Apple only, that kind of platform limitation will be a big (almost certainly fatal) handicap to collaboration software. If it isn't, you need to make that clearer.
A hamburger menu (traditionally used to mean "everything else") on the left, and an ellipsis menu (also traditionally used to mean "everything else") on the right? Oh dear.
Sorry, this is a total showstopper for me. I'll check back when Emscripten actually lets me use more than 1/4 or 1/8 of the CPU.
Yes it does. The UTF-8/16/32 encodings are defined in the Unicode standard (chapter 3.9, page 89), they're not some kind of aftermarket add-on.
"UTF-8 has the possibility of having encoding errors, where things like UTF-32 do not."
Also not true. The set of valid Unicode code points is the same regardless of the encoding (0-0xd7ff and 0xe000-0x10ffff); anything outside those two ranges is just as invalid in UTF-32 as its UTF-8 encoded equivalent would be. A stream containing nothing but 0xff bytes, for example, would be illegal regardless of which UTF you tried to interpret it as.