A prevalent pattern is for IDs to be unique. More than one document has been written about it.
Most any machine one makes or designs one can get so involved in that one is preoccupied with the making or the workings of that machine, one could forget there was a purpose.
Having worked to make Adj viable, in several ways, now this very moment I am not directly facing any of the enterprise software design problems that originally made me want to have Adj. I am sure some will occur sooner or later, complexity is here to stay – just try to understand your CPU chip, all its transistors, how it works, or how it is made.
This made me think though, how do others see Adj? Is Adj
- something to use, or
- something to develop?
If you have been around SVG, XML, browsers, and computer graphics for a while, you may have noticed an upsetting dichotomy:
This is an announcement of new features of the open source Adj framework, which is at version 3.5.6.
For a formal reference, there is the user guide.
What is new: