XML is too verbose and not really very readable by humans, we read it just because we're used to it... it was meant to be read & written by machines, not us.

An eclipse SDL editor plugin would be a very nice thing to have, of course.

So, here is my -1

Besides that I think that a standard SDL-like language is really needed, on my current project we didn't wanted to be reading / writing our configuration files on XML or plain properties files so we embraced GroovyMarkup, then SDL came for HiveMind... so we currently have to deal with two different but very alike syntaxes, this is really a pain.

Not to mention all those other framework's XMLs...

Hey, Howard, when we'll have SDL for every Tapestry descriptor? :D

Let's VOTE THAT!

El lun, 02-08-2004 a las 11:19, Howard Lewis Ship escribió:
All this divisive talk about SDL vs. XML (vs. ???) is getting to be a
distraction from what HiveMind is all about. I think people are very
correct with the idea that the important thing is to minimize the
*amount* of content in the XML, regardless of the _expression_ of that
content. That's where we should be concentrating ... and I have a few
ideas along that line.

Anyway, a +1 vote indicates that you feel SDL should be stripped out
of HiveMind (as a failed experment).  I'm cool with that, as long as
people piitch in to convert the many SDL into XML.

Howard Lewis Ship: -0 (binding)
-- 
Pablo I. Lalloni <[EMAIL PROTECTED]>
Teléfono +54 (11) 4347-3177 
Proyecto Pampa
Dirección Informática Tributaria
AFIP

> In 2010, M$ Windows will be a quantum processing emulation layer for a
> 128-bit mod of a 64-bit hack of a 32-bit patch to a 16-bit GUI for an
> 8-bit operating system written for a 4-bit processor from a 2-bit
> company that can't stand 1 bit of competition.

<<attachment: smiley-1.png>>

Reply via email to