Yes. The same reason Flash Player 8.5 improves rendering speed is because they boilerplate code of actually creating & rendering things has been made open to us.
Same goes for XAML. Allowing more processing to be off-loaded to the hardware and saving the CPU cycles for something important, like processing data is awesome. One could argue that this just allows us to create more unefficient code, and while there is truth to that statement, this process has been going on since before I was born. Just the other day, the garbage man came to my house to drop off a trash can. I started to talk to him, and found out he was a part time programmer for BellSouth. Apparently, writing like... uh... IFel, or some other archiac assembly like language for an old BellSouth telephone address lookup engine. I asked him what is the problem with programmers today? "No respect for hardware." My silent reply? Damn right. Hardware needs to do it's f'ing job, and let me focus on getting my busines logic & design correct vs. worrying if I'll overtax it. It's good to be efficient because eventually we all hit the speed of light barreir for ping times... but I'd aruge optimizations and other such things get in the way of me getting my job done. Hell, just yesterday I'm on the phone with a friend yesterday trying to explain the various ways to reduce the processor hit a component intensive Flash movie does. I'd rather spend that time talking about ways to improve code portability vs. code-efficiency through extended timelines... I say, bring on the hardware accelerated radio buttons... and motion blur the mofos! ----- Original Message ----- From: "Alias" <[EMAIL PROTECTED]> To: "Open Source Flash Mailing List" <[email protected]> Sent: Thursday, December 29, 2005 1:50 PM Subject: Re: [osflash] Out with a bang > Don't they have to come down hard on anything that converts SWF to any > open > format? As long as that exists, someone else can always take the output > and > create a player without risk. For browser playback, XAML is probably their > only worry, but what a worry that is... With that on the horizon I can > imagine that they'll soon be a whole lot more aggressive in protecting the > player. Don't know about doing swf-xaml, but I know there's already a xaml-swf compiler. On the other hand, a swf-mxml parser would actually be an incredibly useful piece of kit, because it would allow developers to move easily between the flex and flash environments. XAML's cute and all, but do we really *need* hardware accellerated 3d radio buttons? Alias _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
