coolfactor

About this... (corrections in bold)

Apple's software correctly transcribes brands such as H&M by using an ampersand rather than the word "and," and the transcription engine correctly renders the ampersand in XHTML.

The transcription engine is not doing anything wrong. The ampersand needs to be encoded. Unless the author meant that the ampersand is being *displayed* in its encoded form?

And for those wondering why the author wrote XHTML specifically, it's because of the strictness needed when sending encoded messages. It's not just HTML, but the much more strict XHTML, which is HTML encoded as an XML document.

I normally defend Apple for having minor bugs, but this one is inexcusable and should have been caught with very basic and routine test cases.

The technology exists now... Apple should focus on fully automated assembly in "micro-factories" located in each strategic market. As demand goes up and down, so does output. Time for a monumental shift in thinking.

Good. This should be a globally-funded nonprofit effort, not dependent on government funding.

Very confused about the mention of "Password Timers".... yet the article is talking about the Verification Code feature that rotates its code once a minute? That feature has been there all along.. it's not new to 15.4. (A verification code is not the same as a password, so calling it a "password timer" is wrong, too). Am I missing something?

This is quite concerning.

First, who in their right mind would implement using only http:// (non-secure)? Second, why was this not caught during basic testing and evaluation?

This is basic stuff.