Does anyone know if Adobe actually took time to implement some of the new features in Lion such as full screen apps or Versions?
Typically, those who utilize Adobe's Creative Suite utilize multiple monitors.
Apple's current Full Screen implementation does not work effectively with multiple monitors.
Additionally, Adobe's applications are dependent upon a menu bar to function effectively, as many of the tools contained within Photoshop, InDesign, Illustrator, Premiere, AfterEffects (and I would presume others as well) are not present purely as a dedicated option within the GUI.
Adobe has also shown to be very considerate about not alienating their user base by changing how to use a product from release to release. Any Photoshop user can pick up any version of Photoshop and do *at least* what they were able to do in the previous versions with no learning curve, with some new possibly better stuff available should they want to learn.
Versions... Yes, that one would be nice, however considering that Versions operates based on CoreData the improvements that you would expect from Versions would not apply (namely, the reduced data storage sizes by containing deltas and injection points) and as an aside all you would have would be Time Machine... something that you already have. That is not to say that Adobe couldn't design their own Versions-like approach and the necessary plugins for CoreData to enable them to operate in much the same way as you would expect from non-project based document types, but that one is quite an undertaking while subsequently limiting yourself to *just* the Mac side of the equation.
For products that share the same code base and simply have a compiler directive to include OS Specific code, the idea of significantly forking the Windows and Mac versions with major additional development that would need to be undertaken within all levels of every tool of every application does not appeal to me as a user, as it means that we would be looking at *longer* release dates or non-concurrent release dates or *more expensive* software or *lower quality* software for every version in the future post-fork.
If Apple had a more complete implementation for their Versions system (such as a filesystem based versioning approach, like NTFS' Volume Shadow Copy, BTRFS' Block Level Versioning or ZFS' Block Level Versioning) rather than relying on solely data accessed and saved via CoreData, than the ability to add Versions support to *any* application would be a possibility. As is, many non-text applications require significant refactoring, assuming that such refactoring is even a possibility considering the type of input and output data.