https://computerhistory.org/wp-content/uploads/2019/10/Apple...
https://thenewstack.io/50-years-ago-a-young-bill-gates-took-...
Perens had accepted a position as senior Linux/Open Source Global Strategist for Hewlett-Packard, which he describes as leaving Apple “to work on Open Source. So I asked Steve: ‘You still don’t believe in this Linux stuff, do you?'” And Perens still remembers how Steve Jobs had responded.
“I’ve had a lot to do with building two of the world’s three great operating systems” — which Jobs considered to be NeXT OS, MacOS and Windows. “‘And it took a billion-dollar lab to make each one. So no, I don’t think you can do this.'”
Perens says he later "won that argument" when Jobs stood onstage in front of a slide that said ‘Open Source: We Think It’s Great!’ as he introduced the Safari browser."
If a literal interpretation of what you wrote allows for something, even though it's clear that you hadn't intended to do so, then it is going to be allowed.
https://www.macrumors.com/2026/01/28/apple-updates-keynote-n...
> "Ryan Lawler of TechCrunch wrote in 2012 "Jobs was right", adding Android users had poor experiences with watching Flash content and interactive Flash experiences were "often wonky or didn't perform well, even on high-powered phones".[9] Mike Isaac of Wired wrote in 2011 that "In [our] testing of multiple Flash-compatible devices, choppiness and browser crashes were common", and a former Adobe employee stated "Flash is a resource hog [...] It's a battery drain, and it's unreliable on mobile web browsers".[10] Kyle Wagner of Gizmodo wrote in 2011 that "Adobe was never really able to smooth over performance, battery, and security issues".[11]" - https://en.wikipedia.org/wiki/Thoughts_on_Flash
[1] https://www.palminfocenter.com/news/9692/palm-joins-adobe-fl...
[2] https://old.reddit.com/r/Palm/comments/ere0c/how_does_flash_...
Giveaways are brutal/ill placed line breaks, zero quotes being curly ones (single and double), -- instead of a en/em dash, missing hypenation or existing one that does not align with typesetting "dis- play", etc., etc.
Why not use an image of the original instead? [1]
Jobs would have never signed off on a typographic eyesore like this. :]
[1] https://www.alamy.com/stock-image-an-advertisement-for-the-a...
https://upload.wikimedia.org/wikipedia/commons/4/48/Apple_1_...
https://archive.org/details/InterfaceAge197609/page/12/mode/...
I really, really, love building stuff for/on the web. When working with founders/clients we'd often start with building the MVP as a PWA, because of how easy it is to iterate and test. (https://untested.sonnet.io/notes/web-and-feedback-loops/)
That said, some reasons off the top of my head in random order:
- seemingly small but UX critical features breaking or not working at all (wake, audio, notifications, scroll breaking).
- most of the users don't know/haven't been taught they can install a site or assume that PWAs are inherently worse
- PWAs are harder to monetise (no super easy way to let the user pay a lifetime licence for the app, customers want super easy, and that's not for me to judge)
- critical, but non-obvious to a non-technical person (and thus difficult to explain) features are unstable or janky on iOS when running standalone/via home screen (example: wiping offline storage every few days).
In some ways things work better than, say 10 years ago, but at the same time there's the *unpredictability*. I really don't want to worry about my app breaking in some impossible to fix way next year. Not, when the app is meant to pay my rent.
Performance was rarely an issue, discounting experiments like running image recognition inside a "service worker" in JS, on iPhone 7 for an AR game I was messing with. That was in 2016 (before Pokemon Go came out and kind... of dumbed down the idea or AR).
