From mboxrd@z Thu Jan 1 00:00:00 1970 From: mru@users.sourceforge.net Subject: Re: future ALSA development Date: Tue, 24 Jun 2003 09:51:46 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <87znk7rjzh.fsf@users.sf.net> References: <3EF77D90.5080209@folkwang-hochschule.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org Joern Nettingsmeier writes: > >>other people might propose XML. then it becomes to a question whether > >>alsa-lib should rely on other libs... > > > > > > I think that XML is too overkill for our purposes. > > true if you only consider alsa. but on most systems, libxml2 is there > anyway. and imvho xml is less a matter of > taste than lisp. and xml is way easier to handle in other > contexts (i'm thinking of auto.configuration stuff etc.) > otoh, the embedded guys will probably not like it, but then memory is > becoming cheaper by the minute, and its additional size will be a moot > point in the very near future. IMO, xml is a piece of bloated, error-prone hypeware. Comparing it to LISP doesn't make sense at all. LISP is a programming language, whereas XML is a markup language, albeit one that has come to be misused a great deal. -- Måns Rullgård mru@users.sf.net ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php