{"id":41520,"date":"2023-12-20T20:47:01","date_gmt":"2023-12-21T01:47:01","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=41520"},"modified":"2024-05-24T11:17:30","modified_gmt":"2024-05-24T15:17:30","slug":"the-original-iphone-demo","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/12\/20\/the-original-iphone-demo\/","title":{"rendered":"The Original iPhone Demo"},"content":{"rendered":"

Fred Vogelstein<\/a> (2013, via Hacker News<\/a>):<\/p>\n

\n

The software in the iPhone’s Wi-Fi radio was so unstable that Grignon and his team had to extend the phones’ antennas by connecting them to wires running offstage so the wireless signal wouldn’t have to travel as far. And audience members had to be prevented from getting on the frequency being used. “Even if the base station’s ID was hidden” — that is, not showing up when laptops scanned for Wi-Fi signals — “you had 5,000 nerds in the audience,” Grignon says. “They would have figured out how to hack into the signal.” The solution, he says, was to tweak the AirPort software so that it seemed to be operating in Japan instead of the United States. Japanese Wi-Fi uses some frequencies that are not permitted in the U.S.<\/p>\n

[…]<\/p>\n

Then, with Jobs’s approval, they preprogrammed the phone’s display to always show five bars of signal strength regardless of its true strength. The chances of the radio’s crashing during the few minutes that Jobs would use it to make a call were small, but the chances of its crashing at some point during the 90-minute presentation were high. “If the radio crashed and restarted, as we suspected it might, we didn’t want people in the audience to see that,” Grignon says. “So we just hard-coded it to always show five bars.”<\/p>\n

None of these kludges fixed the iPhone’s biggest problem: it often ran out of memory and had to be restarted if made to do more than a handful of tasks at a time. Jobs had a number of demo units onstage with him to manage this problem. If memory ran low on one, he would switch to another while the first was restarted.<\/p>\n<\/blockquote>\n\n

Ben Thompson<\/a>:<\/p>\n

\n

The part of the Gemini announcement that drew the most attention did not have anything to do with infrastructure or data: what everyone ended up talking about was the company’s Gemini demo, and the fact it wasn’t representative of Gemini’s actual capabilities.<\/p>\n

[…]<\/p>\n

Google, given its long-term advantages in this space, would have been much better served in being transparent, particularly since it suddenly finds itself with a trustworthiness advantage relative to Microsoft and OpenAI<\/a>. The goal for the company should be demonstrating competitiveness and competence; a fake demo did the opposite.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n