[Golist] Repercussions of Go

[Moses Gunesch]

Well sure, tweening APIs are very useful, and some of them get very  
popular.

However, that doesn't mean that developers shouldn't be offered a  
toolset for building their own tweening APIs instead of having to work  
with other people's ideas, overhead, and limitations.

Also consider this: If both you and I program our own stuff over Go,  
then try to work with each other's code, a lot of stuff will be common  
and familiar, even if we've made up our own syntax or tween classes.  
In fact there's a very good chance that we could mix and match, port  
features easily between our code bases and so forth... all while  
retaining the knowledge and flexibility to be able to work in the way  
we want with it instead of being forced to agree on a single  
monolithic API.

But that's just the party line... everyone else, what do you think?

- moses

On Jan 4, 2008, at 10:52 AM, Rich Hauck wrote:

> Moses is advocating that Adobe take the reins and redo Flash’s built- 
> in Tween engine. In the meanwhile, the flexibility of Go’s package  
> concerns me, as I believe that either:
>>
>> Developers will avoid Go in lieu of Tweener or TweenLite, since  
>> those packages have a defined syntax that larger groups can easily  
>> agree upon
>> Developers use Go and make a slew of proprietary animation engines-- 
>> and in-turn generate a learning curve for anyone forced to use  
>> their engines
>> Someone creates a syntax similar to ZManager.paramsObj(), something  
>> that trumps the current AS3 Tween engine offerings, and that  
>> emerges as the unofficial definitive engine.
>
> What’s everyone else’s take on this?
> _______________________________________________
> GoList mailing list
> GoList at goasap.org
> http://goasap.org/mailman/listinfo/golist_goasap.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080104/702a1acd/attachment-0001.html