-1 karma · joined August 7, 2019
Described issue is not problem of a JSON but engine which parsed it and language which stands behind the parser. Any config format will eventually have same result and same issue.
So forcing programmer to parse every single piece of data for sake of "it's his responsibility" is not a case here.
I also disagree this is in any way programmer responsibility to create standardized way of creating parser for everything. This format gives you nothing but indentation so you are forced to create documentation for everything field, what type it's and what kind of values it takes. Lots of extra work for nothing when you have any other format.
This is something what you may or may not know as Workspace from Windows or KDE but on steroids.
How virtual screens are handled by the OS is different story. As a user of ungodly discussing i3 tailing manager I can only say, problems you described I personally consider as terrible design and putting look over functionality.
Basically this looks like OS X do care only for current screen if it's full screen or for any screen if it's not. What's inconsistent (terrible UX) and hard to use (also terrible UX).