3 ms·
Well, time will tell. If they get it right, people will use it. If they don’t, it will wither on the vine. Pretty darwinian, but This Is The Way. XML Schema
by ChrisMarshallNY 4y ago
Well, time will tell.
If they get it right, people will use it.
If they don’t, it will wither on the vine.
Pretty darwinian, but This Is The Way.
XML Schema is a fiendishly complex, awkward, and verbose standard, but it is very much in use. Personally, I hate it, but I have used it fairly often.
I would like it to succeed, and will use it, if it does; even if it’s ugly. If it doesn’t work, I won’t use it.
My experience tells me that it can be next to impossible to predict what will and won’t work, and there’s probably no replacement for actually putting it out there and trying.
My experience also tells me that the most certain way to ensure failure, is to try predicting the future, and engineering for a very specific one.
Personally, I have had good luck, with an “heuristic” approach, where my designs act as a “lattice” for growth, and I evolve it, as I see the direction the project takes.
The main thing, in my experience, is to never have to go back and change stuff that has already been done. I may do new stuff, in the future, that breaks the API, but I should always honor The Old Ways.
- ChrisMarshallNY 4y ago> The main thing, in my experience, is to never have to go back and change stuff that has already been done. I may do new stuff, in the future, that breaks the API, but I should always honor The Old Ways. I just realized that sentence doesn't make sense. I meant that people will build on an API, and make assumptions to "fill in the gaps." As long as there's nothing in the current API that "codifies" these assumptions, I consider it OK, to add stuff that breaks the assumptions, but I won't go and make changes to stuff I've codified. An example is some work I was doing, with an Apple UIKit API. I was calling a set of functions in a particular order. Apple released a system update that reset one of the settings, so I needed to move the call that affected that setting, to the end of the chain. They never specified the order (nor did they do so, after that, even though they probably should have), so I had no room to complain.