[erlang-questions] idea: service pack one

YC <>
Wed Nov 14 22:58:25 CET 2007


On Nov 14, 2007 7:48 AM, Brandon Black <> wrote:

> > I view things like database and mail protocols similarly to how you
> > (and I) view UIs - these are things that belong in extension
> > libraries, not as some core part of a language distribution.  The
> > popular protocols will change over time, and the popular
> > implementations of those protocols will change as well.  Old
> > implementations will naturally be replaced with increasingly superior
> > abstractions if you let the more external stuff evolve in a darwinian
> > fashion somewhere like CEAN.  Even really good implementations will
> > get replaced by newer ones that follow newer and better best practices
> > that evolve over the years.  Embedding early implementations of what's
> > popular today into the main distro is counterproductive if anything.
> > Once you bundle something with the core, your stuck with it as legacy
> > baggage for a very long time for fear of breaking upgraders, and
> > people tend to use it "because it's there" long after it's a very
> > unrecommended practice to still be using it.  Keep the core as minimal
> > as possible, IMHO.
>

Agreed that libraries should be separated from core.  My point wasn't that
they should be a part of core language or even distribution, but rather
erlang can improve its adoption with the new comers with better support for
conventional databases and other standard protocols than it has now.  Mnesia
is great and all, but it doesn't fully replace rdbms and few newcomers will
start learning erlang by writing a full blown database client (or smtp
client) that they've taken for granted (and never have to intimately know of
the protocols) in other language platforms, even though erlang makes it
easier to do so.

But while we are on the extension point, I also agree with you that the
extension distribution mechanism should be standard (besides  tarballs +
make).  While organic evolution has its merits, IMO extension distribution
is one problem where standardization helps more than it hurts, just witness
CPAN and other variants.  My personal favorite is PLT Scheme's Planet, which
allows you to completely skip the install step by directly requiring the
remote module as if it's local.


Cheers,
yc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20071114/ed1ce965/attachment.html>


More information about the erlang-questions mailing list