I agree they should fix the huge number of bugs in ADE2.0.
However, there are lots they have known about for over two years and shown no sign of attempting any fix.
ADE and for the Adobe DRM infrastructure are a disgrace.
May be worth testing with 1.7.2 as well. Quite a lot of people still use that because of bugs in 2.0
There are lots of bugs in ADE2.0 (and 2.0.1). Try replacing ADE2.0 with the older but more reliable v1.7.2.
(You can have them both installed at once if you like.)
Version 1.7.2, it is a little difficult to find, available on Adobe site for Windows and for Mac.
The forum software is sometimes corrupting the link above. There shouldn't be a blank in 'editio ns.html'. The following redirects to the same page: http://tinyurl.com/diged172
Some people have found ADE trying to upgrade automatically.
It appears (not 100% sure) that if you install ADE2.0 as a new install (not as an upgrade) that your 1.7.2 will continue to run.
Probably best to say no if 2.0.x installation asks if you want to migrate your library.
ADE, the Desktop application, provides a subpar reading experience, to put it midly. There are far better software for the user that may want to read their ebooks in a desktop computer, so one should not expect anyone in their right mind to be using it for that purpose. The uses of ADE that one can expect, then, come down to:
1. Being able to sideload DRM'ed ebooks to your ereader if your ereader vendor did not provide something more appealing, in which case, the quality of its reading engine is irrelevant.
2. A way to test how ebooks will look on an ereader that uses Adobe's RMSDK reader, which most eink based ereaders use and then some non-eink.
Considering that even if Adobe updated their RMSDK, one should not expect even 1% of ereaders out there being updated, having Adobe release only incremental fixes to RMSDK would actually be worse, not better, for ebook producers, as, if anything, one can today get an approximate idea of how bad ebooks will look with only one version of RMSDK around (well, purportedly there are several around, but Adobe fixes so little from one to another that one can obviate their differences).
I do agree Adobe should put some effort in the embarrasment that RMSDK is today, but for the love of god, do only release a new version if the whole reading system has been rewritten from the ground up to be up to today's web engine standards. If they are going to only fix tiny little things, like not blowing up as soon as it finds a media query, please do not bother: we are already bad enough with one single coherently crappy standard reading system.