> On the other hand, if you can be flexible enough to allow quirks on import while not perpetuating them on export, eventually you and other software built with the same philosophy standardize the field.
How? The only thing I can see happening is perpetuation of sloppy use of standards. "Why, why should I change my |-deliminated CSV dialect that requires a double-semicolon at the end of each row, which is arbitrarily denoted by either \n or \r or \n\r when all those programmers will accomodate me, no matter how little sense it makes to do so?
> I do think there’s a point where things are standardized enough that you can safely stop doing that
I agree. And that point was when someone sat down, and penned RFC-4180
Everything after that point, has to justify why it isn't RFC compliant, not the other way around.
How? The only thing I can see happening is perpetuation of sloppy use of standards. "Why, why should I change my |-deliminated CSV dialect that requires a double-semicolon at the end of each row, which is arbitrarily denoted by either \n or \r or \n\r when all those programmers will accomodate me, no matter how little sense it makes to do so?
> I do think there’s a point where things are standardized enough that you can safely stop doing that
I agree. And that point was when someone sat down, and penned RFC-4180
Everything after that point, has to justify why it isn't RFC compliant, not the other way around.