99 karma · joined September 19, 2013
On PyPI: https://pypi.org/project/log_calls/
The two categories of things considered harmful in "Science": "Economics", and "Global Warming Fearmongering". The Eco section, which quotes Milton Friedman as an imagined authority, has just a few entries -- for Rent Controls, Minimum Wages, Intellectual Property, a couple of others. In Software, a long list of "harmful" things with allegedly less harmful alternatives, all of it personal choice (editors & IDEs, again?) and the stuff of eternal flame wars. Thus, SQL databases are 'harmful', but "plain old hierarchical filesystems" are less so -- and so much more fun to query too; SVG bad, PostScript better (really?!); ... You get the idea.
The only advantage I can think of that accrues from using the more common extension is editor support: a user's favorite editor may well provide syntax highlighting and checking, auto-indenting, etc. for `.json` or `.yml` files, but not for `.mdl` files out of the box. You might want to develop `.mdl` profiles (sic) for popular editors.
Any decent parser for the 'true' format will accept either a string or a full filename (including extension) and shouldn't expect a fixed file extension.
Regrettably I can't think of a single example right now, but I know I've encountered many programs that use custom file extensions which have turned out to be just some familiar format after all.
That said, it's another question whether either JSON or YAML is a great choice. I agree with your reservations about both. In fact I've had the very same problem in a couple of development projects, one recently. JSON is friendlier than XML, true, but it's not really a language to think in, even declaratively — too much clutter. YAML is certainly versatile enough, but it provides probably more than you need, and it is... yes, obtuse. Of course, it depends on your intended users; I found it was too "programmerly" for mine. I ended up developing a custom parser for a language with more syntactic sugar than YAML, which has its advantages and disadvantages.
In physical applications, relative to a coordinate system negative numbers have perfectly intuitive meanings. A negative spatial coordinate simply indicates a point in one of the quadrants or octants other than the all-positive-coords one. A negative acceleration means something is slowing down.
I see no good purpose served by special-casing "negative" integers, and many needless ensuing headaches.