[Golist] Go: Scary-complicated?

Moses Gunesch moses at goasap.org
Tue Mar 4 08:56:48 PST 2008


Hi everyone,

So now that the new site is live, let's assess how I did for making Go  
approachable.
Go is actually very simple once you understand it, but before that it  
intimidates people and seems really complicated.

So:
Are the goals of Go still confusing?
Is the presentation of Go confusing?
Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ 
  ?
Is it clear yet that very little is required for the compatibility  
layer – just GoEngine, GoEvent, and PlayableBase/IPlayable – and that  
everything else is entirely optional?
Is it obvious yet that it's very easy to build a tween over LinearGo  
in 3 easy steps or does that still feel like everest?


Here's one idea I had – a swf slideshow with a "next" nav button, that  
would walk you through step by step how Go is structured. Because each  
bit of it is extremely logical and is there for a reason... for  
example, GoItem is there as an abstract base class for any animation  
type, not just tweens, and PlayableBase sits at the very core because  
some things that you can play, are not animations at all, like a  
Sequence. I want that structure to be really clearly presented but I'm  
worried that the Architecture page does not show this simply enough....

thanks,
Moses 


More information about the GoList mailing list