2 ms·
I worked at Palm on WebOS. If this is the same engine we got for WebOS (which is also what Android phones had afaik), it was still enormously power hungry, slow
by vlovich123 6y ago
I worked at Palm on WebOS. If this is the same engine we got for WebOS (which is also what Android phones had afaik), it was still enormously power hungry, slow, unstable, and ripe for security exploits. I’m not sure I’d buy the claim that you met their requirements as security would be a big one, especially since Safari already had a huge attack surface for quite a while on iOS and Flash integration would effectively be increasing that many times over.
- flashnext 6y agoNo partner was sent the new Flash Next engine afaik, so Palm would have had the old mobile port of the existing Flash Runtime, which was pretty slow on mobile.
- amatecha 6y agoI mean, I'd wager that if this person says they "met Apple's requirements" then that's probably because they actually had Apple sign off on a long list of requirements that were indeed met, in a formal fashion. When you're working on a project of that size/importance, with companies that large, you don't typically casually say you "met the requirements" without that having been validated by the customer/partner. That said, I could indeed imagine that behind the scenes Apple had reservations about security which contributed to the canceling of the partnership. Heck, I bet there are lots of reasons that we probably won't get to hear about unless someone involved with that on Apple's side posts about it.
- vlovich123 6y agoI mean no one from Adobe’s side has posted anything. For all we know it could be someone trolling with an anonymous account. By now I might have expected some actual reporting about this if it was at the point where Apple had formally given Adobe a list off requirements. That would be different and you wouldn’t expect to see Steve Jobs blasting Flash continually into 2010. Let’s take it at face value though. I’m also clear that in large companies like these, rumors abound. It could be a junior engineer who misunderstood and these weren’t actually requirements from Apple and it was internal requirements. Could also be stories part of the team believed but missed that they missed other requirements (eg they met the perf criteria but failed on security).