All his reasons are fairly obvious for the technical user and have been discussed in the blogosphere, but I think hearing it from the horse's mouth and at a very high level will benefit non technical users.
I think you overestimate the degree to which non-technical users await, with bated breath, a pronouncement about programming languages from high officials at Apple. I love non-technical users. I was trying to explain to one of them yesterday that they can still use my website even after their school wipes their hard disk, and separately, even though the email address (login) is their home email address and not their…
Thoughts on Flash
61–70 of 522 posts
Re: Thoughts on Flash
#62I love this. Apple clearly laid out their reasoning, using facts and persuasive argument. The world needs more of this. Obviously, there is some spin in the post, and I don't completely agree with 100% of it, but I love the level of discourse.
I agree, but it's really sad that we're at a place where we praise Apple for communicating... like normal human beings.
What's sad is that it's a simple but important standard that isn't ordinarily upheld. It isn't sad to praise anyone for meeting that standard.
Re: Thoughts on Flash
#63Earlier quoted context omitted.
It's called control over the experience something that really shouldn't be a surprise for Jobs. There are literally millions of experiences out there that can't be done with HTML5, CSS and JavaScript. if you want proof, go to theFWA.com and have a look around. For every bad flash solution out there, there are some quite fantastic ones. Flash gives you control of the experience in ways that by any metrics outcompete H…
Forgive me the simple question, but which part of theFWA.com couldn't be replicated in HTML5?
Re: Thoughts on Flash
#64right. And the Finder - a piece of Software central to OSX was using Carbon until... when exactly? At most 6 months prior to when CS5 came out.
iTunes - a corner stone of the iPhone software world? Still on Carbon.
If I hate one thing, it's hypocrisy.
Aside of that, nice arguments and well-written. Also, from this perspective, MonoTouch and Unity might be in the clear too as they are not cross-platform toolkits reducing themselves to the least common denominator.
Re: Thoughts on Flash
#65More good news about 3.3.1 "must write in C, Objective-C or C++" clause: it's made even more obvious here that Apple only cares about commercial middleware UI-driven applications. Those of us with custom toolkits and compilers (and games developers) can probably relax. Though, I wish they would still change the wording. I dislike having to wait for my friend's cat to click the "I Agree" button, since I cannot actuall…
Re: Thoughts on Flash
#66More good news about 3.3.1 "must write in C, Objective-C or C++" clause: it's made even more obvious here that Apple only cares about commercial middleware UI-driven applications. Those of us with custom toolkits and compilers (and games developers) can probably relax. Though, I wish they would still change the wording. I dislike having to wait for my friend's cat to click the "I Agree" button, since I cannot actuall…
Unfortunately in legal situations, it's often the letter of the law not the spirit of the law that carries weight. It's been pretty obvious from the beginning that Apple wanted to block Flash, but not, say, Unity. I think they'll find it hard to only enforce it against certain infringers though. Imagine if a government introduced a law that said no-one was allowed out on the streets after dark, but then only actually…
Re: Thoughts on Flash
#67More good news about 3.3.1 "must write in C, Objective-C or C++" clause: it's made even more obvious here that Apple only cares about commercial middleware UI-driven applications. Those of us with custom toolkits and compilers (and games developers) can probably relax. Though, I wish they would still change the wording. I dislike having to wait for my friend's cat to click the "I Agree" button, since I cannot actuall…
"Those of us with custom toolkits and compilers (and games developers) can probably relax." Which part of the submitted article supports this? (genuine question not snark). I see a lot of flash bashing but nothing indicating you don't have to " write in C, Objective-C or C++"
Re: Thoughts on Flash
#68If I remember correctly, iTunes isn't Cocoa based yet either.
Re: Thoughts on Flash
#69Earlier quoted context omitted.
Which arguments are FUD?
* Flash websites will have to be rewritten because it relies on 'rollovers', which is not part of Apple's 'revolutionary' touch interface: overblown for two reasons - a) few stuff will have to be rewritten (many videos show desktop Flash content working on mobile phones without a problem); and b) this is not a problem with Flash, as any JS/HTML-based interface that relies on rollovers has the same issues. * Flash is…
There are multiple implementations and Apple can tweak how it runs. It is open enough for their purposes.
> Objective+C++ is not open.
He never said it was. He said Apple has several proprietary products but believed the web should be open.
> Flash (SWF) has a fully published spec and anyone can write tools to create, or play, SWF content, without royalties, or without having to respond to any entity.
Yet Adobe has the only full implementation of Flash and if someone else were to try and implement it, it would always be behind the official release (just like Moonlight). And Adobe got lawyer-happy when open source guys reversed the streaming protocol in Flash so nobody is eager to try this anyways.
> Saying Adobe postponed the release dates of Flash 10.1 for smartphones: bullshit.
The fact is Adobe has been boasting about Flash on smartphones since Android first came out and there have been no working devices out except Maemo which totally sucked in every way Jobs described.
There was spin in this article just like his DRM article but I wouldn't qualify anything as FUD.
Re: Thoughts on Flash
#70Remove Flash and notice you wont miss it. More and more websites are using HTML there day's. Removing Flash also improves browser speed and stability (just as removing Adobe Reader does).
I did a lot of Flex developing, but I think it's time to move on.