Skip to navigation

PCPro-Computing in the Real World Printed from www.pcpro.co.uk

Register to receive our regular email newsletter at http://www.pcpro.co.uk/registration.

The newsletter contains links to our latest PC news, product reviews, features and how-to guides, plus special offers and competitions.

// Home / Blogs

Posted on April 30th, 2010 by Darien Graham-Smith

Six reasons why Steve Jobs is wrong on Flash

Jobs-small“Steve Jobs just hates Adobe, personally. That’s all there is to it.”

That’s what I heard, from the mouth of a former Apple employee (who would not wish to be named), shortly after the whole stink about Apple and Flash blew up a few weeks ago. And I can well imagine how Adobe’s persistent refusal to run its business to Apple’s timetable throughout the past decade has been a source of personal infuration for Jobs.

So to me it rings true. It makes more sense than the explanations Steve Jobs wheeled out yesterday in his “Thoughts on Flash”, anyway.

For a start, I think the mere fact that Jobs felt the need to make such a statement is suspicious. A rational decision speaks for itself. A pompous screed appearing two weeks after the fact, insisting on half a dozen different justifications for the same thing, smacks of protesting too much.

And the way Jobs expresses himself does hint at a personal grievance. Though he writes in the corporate plural, there’s nothing businesslike about the way he crows at slipped dates for mobile releases of Flash, sneers at Adobe’s use of one API rather than another (as if anybody cares) and signs off with a catty reference to “leaving the past behind”. There’s an antipathy here that goes beyond dollars and cents.

A sextet of smokescreens

In fairness, Apple has come in for considerable criticism lately, so a defensive attitude is perhaps only to be expected. But put that aside and what remains is curiously flimsy. To me, Jobs’ six ostensible reasons for ditching Flash read more like post hoc excuses than rational explanations. Let’s look at the list:

First, there’s “Open” … second, there’s the “full web” … third, there’s reliability, security and performance … fourth, there’s battery life … fifth, there’s touch … sixth, the most important reason… letting a third-party layer of software come between the platform and the developer ultimately results in sub-standard apps and hinders the enhancement and progress of the platform.

Jobs’ first argument is a brazen double-standard. It amounts to “our phone platform can be closed, but your app platform must be open”, with no attempt at a reason why. Argument two claims that without Flash you’re “not missing much.” That’s very much a matter of opinion, and hardly an argument for banning Flash – indeed, it tilts slightly the other way.

The third argument – “reliability, security and performance” – may sound like a triple-whammy of deal-breakers; but it’s important to realise that Jobs is here casting aspersions over a plug-in that, thanks to Apple, has never existed. Even if the OS X player is buggy (something Adobe strongly disputes), that’s no basis for pre-emptively blackballing a new implementation. As for compiled applications, well, over 100 compiled Flash applications have already been accepted into the App Store under the old developer licence, and so far as I’m aware no technical issues have emerged.

Jobs’ fourth argument is that displaying Flash video can be less battery-efficient than showing H.264, because the iPhone has dedicated hardware for decoding the latter. Adobe CEO Shantanu Narayen has already pointed out the absurdity of presenting this as an anti-Flash argument. If it were a regular rule that software could be banned for doing its work on the CPU, the App Store would be very empty right now.

Fifth comes touch. Yes, some Flash applets and games would need to be rewritten to work properly with a touchscreen rather than a mouse. But that’s hardly a reason to ban them from working in any form. Look at the most common uses of Flash – animated front-ends, simple games and video streaming – and it’s clear that the tweaks needed would be small and simple. When Jobs suggests developers might as well migrate their applications into HTML5, CSS and JavaScript he’s transmitting live from la-la land.

Finally we come to what Jobs considers his “most important reason”, and it’s such a doozy that it’s probably worth re-reading in full:

We know from painful experience that letting a third-party layer of software come between the platform and the developer ultimately results in sub-standard apps and hinders the enhancement and progress of the platform. If developers grow dependent on third-party development libraries and tools, they can only take advantage of platform enhancements if and when the third party chooses to adopt the new features. We cannot be at the mercy of a third party deciding if and when they will make our enhancements available to our developers.

This becomes even worse if the third party is supplying a cross-platform development tool. The third party may not adopt enhancements from one platform unless they are available on all of their supported platforms. Hence developers only have access to the lowest common denominator set of features. Again, we cannot accept an outcome where developers are blocked from using our innovations and enhancements because they are not available on our competitor’s platforms.

It’s a paranoid fantasy. Jobs seems to imagine that if developers had the option of producing applications in Flash, they would all instantly sell their souls to Adobe. It’s actually a back-handed acknowledgement of the attractions of Flash, but at the same time an hysterical leap of logic. Slick, professional applications tend to be the ones that “bubble up” in the App Store and make the most money, so if Flash really is less capable, simple economics should keep native development thriving. Flash would settle into a niche as a tool for simpler applications and games – growing the App Store without diminishing its headline quality.

Steve’s personal platform

And those six dubious assertions seem to be the extent of Steve Jobs’ “Thoughts on Flash”. In fairness, he does identify some valid concerns, even if his response to them seems irrational. I suspect he may find sympathy on points three and six in particular: the spectre of such a polished device as the iPhone succumbing to bugs and shoddy applications inspires an automatic aversion. But that remains an instinct, not an argument.

Does it matter? In one sense, the question of whether Jobs’ arguments and actions make sense is irrelevant. It’s his platform, and if he wants to ban iPhone apps from using the letter D in their name, no one (save perhaps the shareholders) can tell him he’s wrong to do so.

But millions of customers around the world – myself included – have an investment in Apple’s mobile platform, in the forms of hardware, applications, accessories and contracts. When the platform faces a challenge, or an opportunity, Jobs’ response affect us. If he governs wisely, our investment maintains its value, or can even go up (such as when the App Store came to the original iPhone). If he appears to make irrational decisions, to put personal vendettas ahead of sound business sense, that can only stunt the platform’s potential and diminish its value.

Presumably, this realisation is what inspired Jobs to publish his “Thoughts” in the first place — a hope of dispelling the whiff of ugly arbitrariness that’s been hanging around the platform since his anti-Flash diktat first came to light.

But if that was the aim, Jobs has failed utterly. This unpersuasive document, this too-bullish rationalisation, seems if anything to further illustrate the fuzz of unreason that has clouded his vision. To me, as an iPhone customer, it confirms that I can’t expect him to develop the platform in the ways I’d hope, or even in ways I can make sense of.

And that’s why, as I write this, my iPhone contract is being wound up, and a new HTC Desire is on order. And yes, as you probably know — it does run Flash.

Picture: http://www.flickr.com/photos/acaben

Tags: , , , , ,

Posted in: Rant

Permalink

Follow any responses to this entry through the RSS 2.0 feed.

You can skip to the end and leave a response. Pinging is currently not allowed.

31 Responses to “ Six reasons why Steve Jobs is wrong on Flash ”

  1. zooongu Says:
    April 30th, 2010 at 5:38 pm

    Very insightful article… There are alot of Mac Fan boys who need to read this article… What’s more, is I think of how innovation thrives in an open society. In a a society in which I can try and fail (ie.. use what ever tools necessary to build my dream application and if it does not succeed or it does not… it is based upon it own merit… not what STEVE JOBS had decided he does not like… It seems the height of egotism for Steve to try and kIll Flash / Adobe after all many of the designers who use these tools bought his products in droves… and like you I have a phone running Android… and if I get a tablet it will be running Android or Chrome… I wish I could return the IMAC I bought last year… but o-well… he has definitely lost me as a customer of his products…

     
  2. Ben Weiss Says:
    April 30th, 2010 at 5:41 pm

    You are a moron. You completely dismiss for no reason the main problem with Flash. Adobe has a history of making bad software and not fixing their own bugs. If you read bug reports on the Mac platform as we developers do, you would know the degree to which Adobe is responsible for so many of of them. Thank goodness that idiots like you can leave the platform so the rest of us can get to work on great things and not be bothered with more blathering from people who don’t know what they’re talking about. Good riddance.

     
  3. Ganesh Says:
    April 30th, 2010 at 5:54 pm

    If Flash has so many problems, why people are still using it!!! Apparently, if people are using it, it’s ok.. I guess, the only problem with Steve Jobs is he cannot use it on his IPAD or IPHONE.. It’s his problem and not the problem created by Adobe or millions of users using it..
    Just shut up!!!

     
  4. Mark Says:
    April 30th, 2010 at 6:04 pm

    Ahh, nice ad hominem atack there Ben. Totally destroys any credibility you might have had but there you go – keep up the good work!

    As for Jobs, well I find it hard to believe that he’s being wilfully ignorant or that he’s not done his research, so I guess that just leaves blatant deceit.

     
  5. Yasir Says:
    April 30th, 2010 at 6:29 pm

    Having a phone capable of viewing Flash based content is very far down the list when I look for a new phone. I also don’t think for a second that not supporting Flash will in any way hinder the development of future Apps. I will stick to my iPhone thanks.

     
  6. lokash Says:
    April 30th, 2010 at 6:43 pm

    I agree with you Darien in your assertion that this is personal. But to me, Adobe and Apple (read Narayen and Jobs) are one as bad as the other and this animosity is ultimately only going to damage both businesses.

    What Adobe should do, instead of complaining about the decision, is to deliver on what Apple claims to have asked for: better reliability and lower power consumption: That way they’d remove the grounds for complaint and Jobs wouldn’t have a leg to stand on. After all, it’s not as if Adobe lack resources.

     
  7. Nodders Says:
    April 30th, 2010 at 6:43 pm

    Nice inciteful article Darien. Must be some sort of record for having some knuckle scraping “developer” (yeah right) show up to utter some complete some rather embarrassing twaddle as well.

     
  8. john Says:
    April 30th, 2010 at 7:12 pm

    “A simple “Hello World” app created in Flash and compiled to work on the iPhone would take up 8 MB, he said, when it should be no longer than a few KB. (Wired.com verified this figure with two other developers who have tested the iPhone Packager tool in CS5.)”
    ………The full article is on Wired…..
    I’d say that’s a great reason to keep Flash away from my phone. BTW, 100 Flash apps in the App Store out of 200K apps == 0.05%.

     
  9. Nicomo Says:
    April 30th, 2010 at 8:09 pm

    Adobe shouldn’t back down, they should keep developing for Apple until Apple takes them to court or tries – at least the real hackers can have fun getting their apps working on the iDiot devices made by this spoilt fruit.

    Surely the EU should treat this with suspicion – Apple clearly are not being fair to developers who write for multi platforms – in fact they are telling developers – work for us or them. If the EU can force M$ to be compatible with other browsers then surely Adobe has a case against Apple – well at least in the EU.

     
  10. Nick Sharratt Says:
    April 30th, 2010 at 9:49 pm

    The app architecture of the iPhone doesn’t lend itself to plugins or add on for mobile Safari. Despite Opera mobile being available and being ‘quick’ due to it’s server based compression techniques, it doesn’t measure up to Safari in terms of stability and comparability in my experience with it.

    For Adobe to implement flash in a browser on the iPhone, they would need to get into the browser writing business or partner with another browser maker and users would need to choose to use that browser. This would fragment the efforts web designers would need to make to create rich mobile websites even further, damaging the experience for users and actually harming innovation too. I recall the bad old days when Netscape started to be over shadowed by IE and it suddenly became much more tedious developing web sites having to check functionality in multiple platforms.

    To date, that hasn’t been an issue for developing a nice iPhone version of mobile sites and the browsing experience for users has benefited from rapid improvements as a result. YouTube, Flickr, google etc all appear and work in ‘iPhone type’ ways as a result.

    The article rightly points out that flash is usually (pointlessly?) used for little animated graphics, video and ’simple’ games – forgive me for not missing those when I rarely find sites these days which don’t include an iPhone version for any video.

    Flash was always a kludge to provide richer features to web sites which were impractical or impossible with HTML and script, but that was 10 years+ ago and web standards and browser capabilities have moved on. As a result, flash is rapidly becoming a legacy technology which is only filling a few niches still, and more and more of those evaporate as sites are updated.

    It is intrisically inaccessible to many people needing screen readers, it has provided additional attack vectors to hackers and regularly hogs CPU time for trivial things or crashes.

    All that said, I think Apple should allow a flash enabled browser and let market forces kill it rather than act as gate keeper.

    Use of Flash to develop apps is a different issue entirely and having looked at the overheads of developing native iPhone apps, I think Apple should be glad for someone to provide a richer rapid development mechanism – and again, if the resulting apps are poor or crash, trust their users to exert market forces.

     
  11. Adrian Bruce Says:
    April 30th, 2010 at 11:03 pm

    “if the resulting apps are poor or crash, trust their users to exert market forces”
    Absolutely Nick. There are sound arguments against Flash. Why not let those arguments take their course?
    John says he has “a great reason to keep Flash away from my phone”. Fine – he doesn’t have to download such apps. Why stop everyone else from doing so?
    As for Ben, well, if Flash stuff is so bug-ridden, nobody will use it and there’ll be no reason to ban it.
    Relax guys – just let the wisdom of the crowd work and let the people speak.

     
  12. Will Damien Says:
    May 1st, 2010 at 12:43 am

    It seems like the PC Pro favourite- Microsoft, seemingly agrees with Apple on this one. I think that the most telling sign in Jobs’ essay was

    “We’ve been asking Adobe to show us Flash working well on any mobile platform but the fact is they haven’t…”

    Apple like Adobe- the creative suite for instance works even better on a mac than a pc… but Flash isn’t quite there yet in terms of stability needed to run on a mobile device.

     
  13. Peter Brown Says:
    May 1st, 2010 at 9:22 am

    Just like to say I’ve read this post with great interest. With the HTC Desire I can view the pc pro website in full fidelity. When iPhone user colleagues see flash working on Android devices it genuinely starts them thinking that the future of Android devices could be game changers in the smartphone market and like Darien start checking when their contract expires.

     
  14. GoodDoc Says:
    May 1st, 2010 at 10:12 am

    @ Peter Brown.

    What content are iPhone OS users missing from the full fidelity version of the PC Pro web Site?

    Adobe should have taken note when users started installing pulgins that disable Flash to improve the browsing experience, but when you have become a de-facto standard the Apples and Googles of the world have to deal you, not the other way round.

    For the moment at least, I’ll take the lack of a product I don’t miss over over the myriad of different hardware configurations and uncertain software updates that the other platforms currently offer.

     
  15. AS Says:
    May 1st, 2010 at 10:40 am

    Jobs (and Apple) should really think twice before criticizing another company’s software performance – iTunes for Windows anyone? A bloated resource hog riddled with additional programs (Bonjour, Quicktime) that most users probably don’t want or need but are forced to install.

     
  16. Mike Baldwin Says:
    May 1st, 2010 at 5:16 pm

    Apple and Adobe…Both Ars**s.As is Microsoft and all the other technology companies i can think of.There, thats how to be impartial ! :-)

     
  17. Cocoa Says:
    May 1st, 2010 at 8:46 pm

    Adobe beat Apple in fully adopting Mac OS X. By his own words Steve Jobs admits that even Apple has not fully adopted their own OS. iTunes still does not use Cocoa. Finder only adopted Cocoa 8 months ago. When will the hypocritical Jobs publish an open letter to his own development team?

     
  18. Sonny Says:
    May 2nd, 2010 at 3:09 pm

    So that’s what that Bonjour crap is for.

    I lovdxrhe domplixity of the iPhone (havto turn sound off to type properly with it). But my 18 month contract is up next month and I am fed up of it crashing regularly and not being able to watch videos properly – the Youtube player is crap quality.

    The DOJ should force Apple to open it’s platform like they did with Microsoft, so that ppl like Google and Firefox can create their own browsers, flash enabled or not, let innovation thrive, and let users decide which browser they prefer.

    I love using Macs to make music, but this sterile behaviour from a CEO without a suit is irritating.

    Grow some balls Jobs.

     
  19. Chris Brennan Says:
    May 2nd, 2010 at 9:37 pm

    I’m not sure your charge of paranoid fantasy stands up and I don’t think Steve Jobs hates Adobe I think he hates the thought of another company being able to dictate what steps Apple should take next.

    Apple has suffered from having a development platform that they didn’t own before. CodeWarrior was the tool lots of developers used to code for Mac. Everytime Apple released an update there was a chance it would break CodeWarrior. Or new features they advertised would not be available in all applicaitons because CodeWarrior hadn’t been updated to include them. This resulted in delays for key software for the Mac platform. Imagine launching your shiny new OS only to have the first two months of sales flat becuase people are waiting for Adobe to update Photoshop as they in turn are waiting for CodeWarrior to be updated?

    This threat only really went away with the switch to Intel and even with Rosetta to smooth the upgrade path I’m sure many users didn’t upgrade until Intel native Mac apps were ready. So when Jobs talks about painful experience he’s not being paranoid or living in a fantasy land he’s remembering what it was like to let a third-party have a say in the development cycle. He’s remembering the issues that arose when developers weren’t using tools that Apple controlled to make products for its users and he’s making sure that Apple and only Apple is in control of its destiny.

    Apple has already been at the mercy of one developer in its history too and I doubt it’s forgotten what that was like. Back in the day Apple was screwed, royally. It’s chapter 1 in the second volume of Apple fanboy folklore: The vultures were circling and Apple’s executives were meeting with Oracle, Disney and even Kodak with a view to selling up. Then Steve Jobs returned in one last throw of the dice. He went to Redmond and got on his knees – he begged like no multi-billionaire has ever begged before or since. Please Mr Gates could you sub me $100 million and promise to make Office for Mac for another few years? To which master Gates replied Anti-trust issues have I, Office 98 I will make, $100 million dollars I will pull from my arse and Steve, I. AM. YOUR. FATHER. (I might have misremembered that last bit)

    I’ve no doubt that on the private jet back to Cupertino Jobs vowed that he’d never again have to beg another company to save Apple. It’s what Apple is scared of. A Flash based application becomes the ‘killer app’ and Apple’s future is again put in the hands of a third party. But this time not only in terms of the ‘killer app’, but also in terms of the ‘development cycle’. You might argue that the Flash compiler isn’t capable of creating an app with such power, but lets imagine you’re gambling the future of a billion dollar corporation on that decision. Still so sure?

    I’ve no doubt that Apple could wait until there was an acceptable version of Flash that worked well on a touchscreen device, but the question is why should it? Surely it’s better to push an agenda for HTML 5, CSS and JavaScript that can’t fall under the control of just one company rather than simply reward Adobe for its piss-poor efforts with Flash for mobile phones.

    The more Apple has taken control over its destiny the richer it has become, the more secure it has become, the chance of Steve Jobs ever having to beg another CEO for help has diminished by a factor of arround $40 billion. Apple’s attitude to Flash and the Flash complier is based on the fear of reliving it’s history and not one of paranoid delusion.

    I’m sure there will be successful competitors to the iPhone and no doubt they will run Flash. I doubt that many consumers will care. They haven’t so far that’s for sure, if the world were littered with Flash capable smartphones then perhaps you could argue a phone with Flash was essential. It isn’t and, clearly as far as consumers are concerned, it isn’t.

    Of course, the cynics view is that none of the details actually matter at all and Steve Jobs is simply refusing to cede a revenue stream to the web. All those thousands of simple games on the app store that cost 59p? Apple gets a 30% cut of the take. Why on earth would you let people get something for free when they are clearly willing to pay for it?

     
  20. Windywoo Says:
    May 3rd, 2010 at 4:05 am

    Jobs is flat out wrong on one point. He claims that Flash isn’t working on a single phone. The HTC Hero and Nokie N900 both run Flash.

    The reason Flash ran so poorly on the Mac was because Apple never allowed browser plugins the same freedom Windows does. This meant Flash had to rely on the browser for all it’s drawing to the screen, and therefore was instensely CPU based. And of course there were plenty of badly made Flash applications that could crash the browser. But can Adobe be held responsible for what developers do with their tools? Would you blame Apple if someone used Objective-C to write a virus?

     
  21. David Wright Says:
    May 3rd, 2010 at 10:15 am

    As a developer and web developer, I hate Flash, it is a pain and it doesn’t bring much, if anything, that you can’t do more easily elsewhere.

    As a user, Flash is a resource & processor hog.

    One of the few sites I use Flash on is Kongregate (I generally run with a Flash blocker in my browser – either FlashBlock or ClickToFlash on Firefox and Safari respectively). There, I like to play Bloons TD 3 & 4. I also have Bloons TD 3 on my iPhone.

    On my desktop PC (4 cores, 4GB RAM), Blons TD 3 grinds to a halt eventually. On the iPhone, it grinds to a halt as well, but much later than on the Windows PC!

    With 4 times the clock speed and times times the number of cores, Flash can’t keep up with an iPhone version of the same game?

    And that is even before you get to things like Flash Cookies and Flash’s general lack of security (well, Adobe’s lack of security, Reader isn’t much better).

    Flash has become an anachronism, outliving its usefulness. A lot of Flash’s use on web pages is down to lazy developers, who can’t be bothered to learn how to do jobs properly.

    My last project used a set of drop-down menus, filled from a MySQL database, over PHP, outputting pure HTML and CSS. A parallel project used the same drop-down menus in Flash. The page took 10 times longer to load and the drop-down menus stuttered and were not as easy to use or maintain as the CSS ones. It also took longer to implement them in Flash…

    That is the thing that annoys me most about Flash, its use in inappropriate situations.

    That said, about 2% of sites I visit need Flash objects actually enabled in order to use them, so I don’t really have any problems with blocking Flash – it keeps the performance on my computer up as well – 20 tabs with blocked Flash content sitting in the background don’t grind my PC to a halt, like the same 20 tabs with Flash enabled…

     
  22. Steve Cassidy Says:
    May 4th, 2010 at 12:30 pm

    The missing balance point here is; how good a citizen have Adobe been on the Windows platform? Are they a paragon of virtue who only slip up on the Mac? Answer: No. Acrobat has become so sucky that a rich variety of workalikes have sprung up, which don’t fill up every user’s profile on the machine with bloated updates, don’t persistently interrupt workers to demand yet another isntall, don’t use a website that makes shoddy attempts to bait-and-switch punters into buying the full version… In order to be worthy of support versus the undoubted single-mindedness of Jobs, Adobe have to show some form of progress and responsiveness to users, not just developers or shareholders. The FEAD optimiser is not the sign of a good platform: as I always say about anyone’s software – if 7-Zip are doing a better job for nothing what’s your excuse? A question Adobe fail miserably with, whether one considers the Apple part of the market, or not.

     
  23. Jon T Says:
    May 4th, 2010 at 1:30 pm

    As someone who has been a developer on various platforms for nearly 30 years I’d like to say that I’m really p****d off that I can’t use my existing skills in Z80 assembler or Sinclair ZX81 Basic to develop iPhone apps. It’s just not fair.

    Seriously though, I’ve worked on a number of systems, PC based and mainframe in those 30 years that have used a third-party layer to then create “native” code and to be honest, all of them have completely sucked. If there’s anything out of the ordinary then you have to get your hands dirty in the bloated code that it’s produced. Nightmare, nightmare, nightmare.

    So if any developers want to produce apps for the iPhone/iPad and take advantage of the biggest mobile market there currently is then they need to Gear Up (with a Mac and native SDK), Gen up (with the books) and shut up (get your head down and get on with it instead of constantly whinging and flapping your arms in the air).

    Everything has its place and its time, nothing goes on forever. The future belongs to those who retrain for it, those who don’t will whither and die. Simple.

     
  24. Neal Says:
    May 4th, 2010 at 2:47 pm

    Such a stupid article. They have thrown a lot of mud at Apple customers and continue to be a main cause of security concerns on Windows.
    Adobe sticks.

     
  25. Craig Says:
    May 4th, 2010 at 5:48 pm

    it feels like windows users aren’t content with just having a more stable flash for their pcs. they also have to come over to mac side, buy iphones and macs and then bitch about apple’s criticism of adobe and their flash standard. it’s like the ugly american visiting communist china and criticizing the chinese for their unfree lifestyle.

    i haven’t heard a single good thing about flash since this all began to unfold except for its ubiquity. kind of like porn.

     
  26. Dave93 Says:
    May 5th, 2010 at 11:49 am

    Apple have been up-front about not supporting Flash on iDevices. Why did you buy one knowing this and then bitch about it?
    Apple doen’t have to do anything that they don’t want to do. iPhone is their design, they own it, you don’t have to buy it.
    Stop whining, sell your iPhone and fool yourself that some other phone is ‘better’.
    Sales figures speak for themselves, they have sold more iDevices than you have readers – go figure.

     
  27. Dave93 Says:
    May 5th, 2010 at 11:51 am

    Oh look! All your advertisers supply Flash banners for your site. Now I understand. Lazy, lazy, lazy. Nothing gets better by staying the same.

     
  28. Andreas Says:
    May 5th, 2010 at 9:58 pm

    This is just a personal vendetta against Adobe from Jobs. I’ve worked on most of my Flash projects with an iMac, and i’ve watched youtube clips on the iPod touch, haven’t had any problems with either of them.

    But the real deal here is PC vs MAC. Steve Jobs calls Flash Pro-Pc, and he is implying both hidden and open that Flash is bad.

    ***Offensive comment removed***

     
  29. David Wright Says:
    May 6th, 2010 at 8:22 am

    @Dave93 – Flash banners? I don’t see them… Oh, wait, I have a JavaScript blocker and a Flash blocker on my desktop browser… :-D

    I don’t run an ad-blocker, but if a site is stupid enough to use Flash adverts, they only have themselves to blame, if they don’t get revenue…

    That said, they seem to substitute JPG and GIF ads, if you don’t let them run JavaScript from places like doubleclick.

     
  30. Bjornline Says:
    May 6th, 2010 at 11:04 am

    @David Wright – you’re flash dropdown was 10 times slower than the same in CSS?? You’re obviously not going to be in business for long.

     
  31. David Wright Says:
    May 10th, 2010 at 7:33 am

    It wasn’t my Flash drop down. I wouldn’t touch Flash with a 10′ barge pole!

    But, by the time the page had loaded, downloaded the bloated Flash elements and initialised them, the user could have selected the menu item they wanted on the CSS version…

    This is just an example of where people tend to use Flash, when there are better, easier and faster alternatives.

    The problem is, Flash is slow, bloated and used in the wrong places. It isn’t without merit, but it is too often misused.

    Add into that, its Security flaws and Adobe’s lackadaisical attitude to fixing the problems and Flash is currently a nightmare.

     

Leave a Reply

Spam Protection by WP-SpamFree

* required fields

* Will not be published

Authors

Categories

Archives

advertisement

SEARCH
SIGN UP

Your email:

Your password:

remember me

advertisement


Hitwise Top 10 Website 2010