[erlang-questions] idea: service pack one

Roberto Saccon <>
Wed Nov 14 00:54:12 CET 2007


I really don't understand why you want flash for the GUI, unless it is
a pure AIR project or a specialized video / audio application. But if
it is in the browser, then I see only disadvantages:

- flash is not part of the browser DOM
- Flash is a usability and accessibility nightmare
- flash requires Designer comfortable with the proprietary Adobe
tools, if you want to customize the look and feel
- Flex is like Java: because of its complexity you need specialized
tools  (Flex SDK, is eclipse + plugin, goodbye emacs) to handle it

and I agree with Bob, if flash, and if as open source as possible,
than haXe (it is also more performant than AS3 since yesterday, if you
follow the haXe blog)

On Nov 13, 2007 9:36 PM, Bob Ippolito <> wrote:
> On 11/13/07, Yerl <> wrote:
> > Hi !
> >
> > >       repeat after me: client = flash in the browser, server = erlang.
> > > Intermediate protocol = flash AMF
> > >
> > >
> > Cool slogan, but I prefer this one :
> > Repeat after me : client = flash in the browser with OpenLaszlo*, server
> > = erlang
> > Intermediate protocol = UBF**
> >
> > * http://www.openlaszlo.org/
> > ** http://www.sics.se/~joe/ubf/site/home.html
>
> That's a nice dream, but OpenLaszlo doesn't support AS3 (SWF 9) so it
> can't talk arbitrary TCP (UBF) and it doesn't have the same speed or
> capabilities as you'd get from the Flex 2 SDK. If you were adamant
> about going with something non-Adobe I'd think more about haXe than
> OpenLaszlo.
>
> I don't really see the point in talking UBF when AMF is going to be
> more efficient for the client to deal with, and the code would be more
> generally useful since it's a (de facto) standard.
>
> -bob
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://www.erlang.org/mailman/listinfo/erlang-questions
>



-- 
Roberto Saccon
http://rsaccon.com



More information about the erlang-questions mailing list