3 ms·
Okay, I don't get it: why does everyone assume that having the same syntax for trees automatically means you have to put everything in the same tree?
by CodeMage 14y ago
Okay, I don't get it: why does everyone assume that having the same syntax for trees automatically means you have to put everything in the same tree?
- alexchamberlain 14y agoHaving reread the comment, I can see what you mean. There are massive advantages to 2 different syntaxes.
- weavejester 14y agoWhat massive advantages are those? I mean there are obvious disadvantages in that you have to write two different parsers, and learn two separate syntaxes. What are the advantages?
- matzipan 14y agowavejester, for the sake of not reposting:read below.
- weavejester 14y agoSo if I understand you right, you're using XML for data because it's well known, and you've created HSS because XML isn't really suitable for styling? Presumably that means you're prioritising developer familiarity over architectural simplicity?
- matzipan 14y agoNo. XML is clear and precise. It supports namespace extensibility. It also provides a very big ecosystem that AXR actually use.
- weavejester 14y agoI'm not certain what you disagree with. XML has a big ecosystem, but presumably you felt it wasn't suitable for use as a styling syntax, otherwise you wouldn't have used HSS? XML is clear and precise and extensible, but it's not exactly known for having a simple syntax, right? So aren't you choosing XML primarily because of the ecosystem and tooling?
- matzipan 14y agoI'm not sure what your point is. I consider XML proved itself as a reliable data layer. JSON is not considered because it does not even supports attributes and extensibility. I would really appreciate if you would consider contributing some nice ideas. Come over to the mailing list :P
- weavejester 14y agoI wasn't leading to a particular point, I was just wondering what your design philosophy was. By choosing XML you're using a syntax with a wide ecosystem and very good tooling, but you're given up some simplicity in your design. Presumably you consider this to be a good trade-off, and I don't necessarily disagree with that choice. My concern is that in order to compete with an existing standard, a technology either needs to be a considerably better, or trivial to substitute for the old standard. XML/HSS seems to satisfy neither criteria, clinging to familiarity on the one hand, but having a high barrier to adoption on the other.
- matzipan 14y agoWe are going to give this a second thought.
- deleted 14y ago[deleted]