>> I would just use my custom version of BXMLSerializer to process all >> BXML files whether they are official '.bxml' files or '.ebxml' >> If the BXML file doesn't contain any 'Transformable' objects, then it >> will behave in exactly the same way as the official BXMLSerializer. > > I think this kind of forking could be a healthy way to add "exotic" features > that might skew the perception of that the Serializer interface encapsulates.
Not sure what perception you are referring to. Can you clarify? IMO forking in any capacity is not "healthy". It only serves to fragment the code and community. Prototyping - yes. Forking - no. G
