[erlang-questions] idea: service pack one

[YC]

Whether it's flash or ajax or other platforms, it simply lives outside of
erlang.  I think it makes sense for erlang to focus on its strength in
server development and interfaces, rather than trying to dictate a
particular UI solution of which it's not a part of, thus allows developers
to make their own decisions.  But certainly supporting the necessary
protocols will help with that regard :)

But if we are talking about tackling protocols, then IMO some other ones are
more important (for new comers such as myself) -

- better ODBI support (specifically prepared statements)
- official native database connectivity support for various databases -
including prepared statements as well
- official support for other inet protocols such as smtp, imap, etc.

And I'm also interested to see leex being included in official distribution
sometime in the future ;)

My 2 cents,
yc

On Nov 13, 2007 4:49 PM, Yariv Sadan <yarivsadan@REDACTED> wrote:

> I agree with Roberto. Unless your UI needs to display
> audio/video/vector graphics/animation, you should avoid
> Flash/Flex/OpenLazlo and use plain old HTML + Javascript. HTML content
> is searchable, browsers are ubiquitous, and practically everyone knows
> HTML whereas relatively few programmers know Flash (which is also
> proprietary, btw).
>
> My (not-so-shocking) take is that, if your Erlang app needs a UI and
> you don't need front-end features that are can't be implemented in
> HTML/JS, you're better off using ErlyWeb :)
>
> Yariv
>
> On Nov 13, 2007 3:54 PM, Roberto Saccon <rsaccon@REDACTED > wrote:
> > 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 <bob@REDACTED > wrote:
> > > On 11/13/07, Yerl <yerl@REDACTED> 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<http://www.sics.se/%7Ejoe/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
> > > erlang-questions@REDACTED
> > > http://www.erlang.org/mailman/listinfo/erlang-questions
> > >
> >
> >
> >
> > --
> > Roberto Saccon
> > http://rsaccon.com
> >
> > _______________________________________________
> > erlang-questions mailing list
> > erlang-questions@REDACTED
> > http://www.erlang.org/mailman/listinfo/erlang-questions
> >
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20071113/51a291c4/attachment.htm>