Lee Brimelow
theflashblog.com · Personal blog · on HN since 2008
Lee Brimelow, an Adobe Flash platform evangelist, writes about Flash and its dispute with Apple over developer restrictions.
What HN saysHN links his Apple post and its thread; commenters note a porn example was pulled with an apology, and discuss Flash's hardware acceleration limits and multi-touch.
16HN people shared it
8linked it in comments
8stories submitted
347story points
16 years agolast shared
2008people per year2026
Most-shared posts
- 1The iPad provides the ultimate browsing experience?3 people · 5 points · first shared 2010 · 3 comments on HN
- 2Post 16413 people · first shared 2010
- 3Apple Slaps Developers In The Face2 people · 229 points · first shared 2010 · 143 comments on HN
- 4Adobe announces Flash Player and AIR for Android1 people · 60 points · first shared 2010 · 39 comments on HN
- 5Some questions about HTML 5 video1 people · 27 points · first shared 2010 · 4 comments on HN
- 6Thoughts On Apple’s HTML5 Demos1 people · 14 points · first shared 2010 · 12 comments on HN
- 7Flash is being redefined1 people · 8 points · first shared 2009 · 1 comments on HN
- 8Flash Is Not Designed For Touch?1 people · 2 points · first shared 2010 · discussion on HN
- 9Normal Flash running in a touch-based device (video)1 people · 2 points · first shared 2010 · discussion on HN
- 10Post 16781 people · first shared 2010
- 11Post 4631 people · first shared 2008
What HN people wrote when they linked it
JacobAldridge · 2010-01-30
Here's the original from the flash blog - http://theflashblog.com/?p=1703
Not surprisingly, the porn example has been yanked with an apology.
Also worth noting the original showed 10 example, not the four in this link, so the porn wasn't quite as obvious (1 of 10 v 1 of 4, and the final one at that).
ottbot · 2010-04-09
A link to the large HN thread on the original blog post
http://news.ycombinator.com/item?id=1253490
The actual blog post:
http://theflashblog.com/?p=1888
ekiru · 2010-02-21
Adobe's platform evangelist claims( http://theflashblog.com/?p=1641#comment-639881 ) that the reason they can't use h.264 hardware acceleration on OS X is due to restrictions on browser plugins, which implies that it does not have full access to the local system.
fatjonny · 2010-02-02
My guess is that not very many people are talking about it because with Flash 10.1 Adobe added support for multi-touch. Once Flash becomes available on a lot of devices that support multi-touch, you will probably see developers adding proper support to their games. If a mouse is present, use it. If multi-touch is supported, use it. And so on. Granted, the current support has problems in some browsers and on some operating systems, but that will (most likely) only get better as long as the multi-touch input information is available through the browser.
Some more information on multi-touch support:
http://theflashblog.com/?p=1678
mrtron · 2010-01-30
The direct link:
http://theflashblog.com/?p=1703
Notice the missing image now. In my opinion, even a weaker stand than having it included.
eonwe · 2010-01-28
In http://theflashblog.com/?p=1641 the Adobe developers seem to complain about lack of possibility to use hardware acceleration on OSX. Yet as you said, Windows Flash has been fast the whole time. Could someone better versed in plugin development tell us if there is a difference in how the browser plugins are done between OSX and Windows (drawing the video part perhaps?).
Or what else could create the difference as I would think that much of the Flash VM code would be identical between Intel OSX and Windows?
amadiver · 2010-01-16
Apple doesn't have a public API for Adobe to hook into to allow for hardware acceleration. As far as I know, there's nothing Adobe can do to remedy that situation.
Adobe wants to bring better video performance to the Mac, but Apple is not supporting them.
Here's the source:
http://theflashblog.com/?p=1641
jdowdell · 2008-10-30
The key is that file dialogs now only appear in response to a direct user action, not a mouseclick. The old utilities will need to change to reflect this.
More info on the reasons for the change:
http://theflashblog.com/?p=463
Info on how we at Adobe fell down in identifying non-customers who would be affected:
http://blogs.adobe.com/jd/2008/10/alerting_customers_of_customer.html
jd/adobe