23 karma · joined October 30, 2008
Yes, Mac performance can be an extra challenge -- think of discussions in 3D, video-editing, or gaming communities. Things get more complicated when you're in a browser -- particularly on a Mac, you can see changing performance when changing browsers. Video will continue to further improve on PCs with hardware decompression, but on Macs Adobe is still hoping to persuade Apple to open those APIs to browser plugins. Adobe's own goal is to make things transparent across hardware/OS brands. And Adobe is interested in adding authoring-support for "HTML5": http://blogs.adobe.com/jd/2009/06/adobe_on_html5.html
(Apple APIs let QuickTime use hardware decompression. Adobe Flash has been seeking permission to do the same....)
"Use the system's video" sounds attractive, but just pushes the problem down the stack. Your mileage may differ, but I've seen people try it before....
(I appreciate the point you made above about font creators feeling fairly compensated for use of their creations though, thanks.)
(I think Apple may have finally added an API which browser plugins can access for their text-to-speech, but I'm not sure how many people have moved over there yet.)
Flash reconciles various needs, from indy creatives to high-budget publishers to ordinary consumers to videographers to anyone seeking a means to communicate their beyond-text ideas to an audience.
Reconciliation of all these interests is a difficult task. If Adobe were to mess over any of these constituencies, Adobe would pay the price.
Who paid the price for HTML4's confusion over OBJECT and EMBED tags? The responsibility was not as direct.
It's quite possible that someone has a minority experience, where it doesn't work. First steps are to check the integrity of the applications (it's legit CS4 direct from Adobe?), then any customizations to the system that may cause it to act differently than others. It's to everyone's advantages to document all meaningful Snow Leopard differences.
There are various libraries to make different types of "3D" faster to develop in Flash. Each has their proponents, their own best-uses.
Some of the other comments here are weird... better when you clearly bet on your words with your name!
Player 8 skipped Linux because it was an interim release with a better graphics engine, and was replaced shortly by Player 9 with a faster logic engine. Unfortunately this was during the same time that YouTube first became popular. Historical notes here: http://blogs.adobe.com/jd_archive/archives/2006/08/linux_obs...
"Linux is a second-class citizen for Adobe" Nah. There's not much chance of revenue for Creative Suite porting, but tools like Flex Builder, and runtimes like AIR, all bring Linux to parity... for instance: http://blogs.adobe.com/jd_archive/archives/2008/03/what_airl... http://blogs.adobe.com/jd/2009/05/linux_journal_readers_choi... http://blogs.adobe.com/jd_archive/archives/2007/10/flex_buil...
The explosive thing is next year's devices -- both mobile and home wallscreens -- which use Linux operating systems in higher proportion than do laptops. Check out openscreenproject.org for context on how important Linux has become at Adobe.
It is... the context menu always holds at minimum a "Settings" link.
For "Why is it on a webpage instead of in the SWF?", it's because Flash is part of a webpage, and is often not sized large enough to display a dialog. Unlike a browser, Flash has no chrome of its own -- it's a component.
For "Why isn't this integrated with the new browser privacy controls?", this is a work item now that browsers offer privacy controls... a Mozilla example: https://bugzilla.mozilla.org/show_bug.cgi?id=508167 https://bugzilla.mozilla.org/show_bug.cgi?id=290456
<em>"The point here is that we can't allow such a fundamental piece to the future of the Internet rely on plugins."</em>
He doesn't establish this conclusion. Recent Google examples (Gears, O3D) show that it's useful to be able to add features to browsers without requiring a complete browser change. Using common cross-browser functionality seems a benefit.
(I can't tell what "FUD" he sees in my blogpost, either. I spent time reading, but wish he had backed up his claims.)
Much of the WhatWG evangelism tries to portray these proposals as a done deal, using phrases like "the HTML 5 standard". But none of us today know how that process will eventually turn out.
The browser vendors within the WhatWG have been trying to define a multimedia engine for years... phrase "HTML5" first got on my radar four years ago: http://weblogs.macromedia.com/jd/archives/2005/06/html5.html
The W3C has bought in to the WhatWG's work, but there's much ambivalence too, particularly as it attempts to rewrite existing Standards and Recommendations (URLs, accessibility), and how editorial control is so focused in so few hands. Hard to say at this point how it will all turn out. Bottom line, what we conveniently call "HTML5" here is not necessarily what a future "HTML 5.0 Recommendation" may be. (Or, more tersely, "don't jump the gun. ;-)
By the way, who are you? I remember researching the handle "johnnybgoode" a year or two ago, but this Hacker News account is recent. It's funny to see people arguing about how "open" they are when they keep their identities hidden... attaching your reputation to your opinions raises their value. You can hide if you wish, but why not open up...?
The stance that "images have no place on the Web" is the oldest of the lot, dating back to Netscape 2.0 days... it's hard to remember or even believe now, but people did rail against the IMG tag.
Back in the late 90s there was much argumentation that "things shouldn't move on webpages". This has died down as people have realized how motion can help clarify interfaces (iPhone's intertial drag helped lots), but we're still not at the point of universal acceptance that animation helps increase the total number of people who find the message accessible.
My point was that the arguments against richer interfaces have died down, as the browsers slowly advance to bring such abilities within reach. There will always be criticism of the leading edge, but Silverlight, iPhone, and "HTML5" have each helped convert camps away from the belief that only permissible medium is lengthy English text.
(SEO has had the gosh-darnedest amount of misinfo spread about... search engines have reached inside SWF for years and years, as the old Slashdot example query of "'contrary evidence' filetype:swf" showed. Start by visualizing the terms on which people will likely seek your services... research the competition you have for the first ten Google hits on the term... then optimize your pages for those terms in the usual way, as recommended by the search engines' guidelines. The "every little bit of dynamic text" fascination is starting to bite Ajax now too, so I have hope it will soon go away. ;-)
jd/adobe
But it has since been misread by many as comparing the codecs and their capabilities.
Chris Di Bona was essentially correct when implying that the pre-2001 type of innovation in Theora/VP3 would not be technically persuasive to modern content sites.
jd/adobe
I agree with you, though, that it's weird to discriminate against such large audiences.
jd/adobe
Basically, the rap is that running one set of HTML/JS/CSS instructions atop varied browser brands, with different implementations and edge-cases of those specs, ends up pushing browser-vendor costs onto the backs of content developers.
(And Flash-enabled mobile phones outnumber recalcitrant Apple iPhones by a factor of 40:1 or so. But we at Adobe would still like to support that popular walled-garden, if permission is granted for us to do so.)
jd/adobe
People do choose to install Adobe Flash into their varied browsers, and they do so successfully and rapidly. It is a real capability in the world today.
For every authoritarian iPhone sold, there are forty-odd Flash-enabled phones sold. Not ubiquity yet, but we're getting there.
Browser vendors could indeed improve plugin communication for things like prefs-setting, cookie-blocking and so on. Instead Opera, Mozilla, Apple and Google are on a dysfunctional goosechase with VIDEO.
<em>"If your web app requires some plugin you WILL lose at least a small part of your target audience."</em> That's true. But it will be more accessible than requiring a browser update, or change in browser brands.
Browser plugins let people choose their favorite browser brand, without losing functionality to other brands of browser. It's cross-browser functionality. Plugins enfranchise minority audiences, and makes it easier for minority browser vendors to compete.
jd/adobe
Access to the official vocabulary classifications is through the HSK program: http://www.china.org.cn/english/MATERIAL/105441.htm
But there are words, then there are idioms, and there are sentence patterns... if you can afford it, the Pimsleur series is unsurpassed for mastering a series of basic sentence patterns.
The John Francis books are useful orientation. If you're studying, the New Practical Chinese Reader series is extensive and helpful.
Veronique Brossier has a good intro to it all: http://www.insideria.com/2009/03/flash-text-engine.html
More examples & info: http://labs.adobe.com/technologies/textlayout/
jd/adobe
There's no need to reflexively push back against Flash. You can learn it. You're not left out. You can open up.
jd/adobe
They should actually be speaking of "what level of CANVAS support", because there are different implementations among different browser brands, versions, and possibly operating systems. Whenever there's a common spec with multiple implementations, some solid conformance testing is vital before starting development.
(I'm not too concerned about the lack of "graceful degradation" here, because it's more of an enthusiast piece, "look what I can code", rather than something solid to deploy out to the general public. Different priorities.)
jd/adobe
tx, jd/adobe