SMF Development > Next SMF Discussion

Package Manager needs more intelligence

<< < (8/8)

青山 素子:

--- Quote from: Fustrate on November 10, 2011, 01:45:12 PM ---Just adding this on the pile, I'd like to move away from XML towards something more like YAML or JSON. XML is just way too verbose for most things, in my opinion... source code edits, sure, but package-info.xml is ugly as hell.

--- End quote ---

Both JSON and YAML seem bad fits IMO for replacing the package format. Properly done, XML is actually really useful. Sadly, XML is rarely done right and usually turns into garbage.

YAML seems particularly bad as it relies on indentation to express hierarchy. If used for marking code edits, it could make for some messy code. For an info file alone, it might make more sense, but I just don't see it being as friendly to those starting.

JSON just doesn't seem to make sense as a replacement for the code edit stuff.

Either way, if you keep XML for the operations stuff, why would you force a different thing for the package info files?



--- Quote from: Fustrate on November 10, 2011, 01:45:12 PM ---Hopefully source code edits will be greatly reduced in the future, eliminated for most things in favor of events (hooks).

--- End quote ---

It'll be interesting to see how well the "hooks" hold up in the future as more and more stuff uses them. I forsee a ton of hooks being added to cover every possible scenario resulting in either huge code flow tracing issues and a lot of mess when developing.

Fustrate:
Honestly, if we did source code edits, I would prefer to do them with diffs... but that's going way too far for most SMF programmers.

I think YAML would be more friendly - it's a much more human-friendly format, the only thing you *really* need to remember is to use spaces instead of tabs, although we can easily alter a YAML parser to support tabs.

Navigation

[0] Message Index

[*] Previous page