Bullllllssshhhhiiiiiiit. I work in industrial augmented reality (Daqri). Here is an actual task I, or someone else, actually has to do someday: I have a steel

Bullllllssshhhhiiiiiiit. I work in industrial augmented reality (Daqri). Here is an actual task I, or someone else, actually has to do someday: I have a steel mill with 24000+ sensors distributed over ~20 machines and/or stations. I need to put the sensor readings into AR space as callouts over the relevant machine and/or station, as well as the results of any secondary processing of those sensors (aka, historical trend analysis, error predictions, etc), as well as ways to view and browse existing documentation of those machines, stations, sensors. In order for the AR-based HMI to be effective, you're going to have to tweak and polish each machine/station's AR HMI. Then I have to do that to the facility that uses the steel this facility produces. And then the facility that uses the steel products THAT facility produces. As each of these facilities was independently constructed, sensorized, and upgraded over the last few decades, each one has it's own differences and quirks, and although there are some solid and reliable standards, there's more than one and many of them are deliberately hard to integrate in order to create lock-in. The only way I can imagine possibly being successful at this is with a framework that makes it easy. So... Either the author has never had to do same-same-but-different over and over and over again, or we have different ideas as to what a framework is. PS - This reminds me of the defaults/no-defaults debate, which I think ends up actually just being "stop working with code that has 'defaults' that are hard to change" - which I'd say mean they're not actually defaults.