Let me chime in. I'm sorry, this is going to get long.
tldr; we humbly appreciate all of the support from our community and customers.
USB support is difficult and it IS being worked on. It's a matter of how the device is advertised to the operating system and how much we can do about it. This work is going into Wine as HID implementation. This should unify the various different ways devices are discovered and make the functionality become nearly 'seamless' assuming the device shows it is present in a sane way. Our developers are taking the lead on this work though many more from the Wine community are contributing.
AutoCAD applications are traditionally a touch and go deal. We have seen more and more begin to work with CrossOver (and Wine) recently and believe that as Wine matures, more applications will work. AutoCAD has not yet been on our radar as something to target because of the amount of work it would take to get it fully functional. However, as Wine improves overall, CAD applications work more and the amount of work it would take to polish this series decreases. Essentially, it gets closer and closer to being reachable to where we could assign a development team to it. It's not there yet, don't read too far into the tea leaves; but it's a series we discuss often.
The 64 bit article is a work in progress. It's not meant to brush off the need for 64 bit support, it's meant to be a reference point for all the people who read and watch our forums regularly. That way when someone comes forward and asks why we don't have 64 bit support (yet), it's laid out directly from us. I haven't gotten it completed; I honestly hope the work to implement 64 bit support matures enough to include it in CrossOver so that we can take that article down. We know that 64 bit support for applications is more than a little necessary and we talk about it weekly if not daily (this week CrossOver 15 and Wine 1.8 are on our minds). Know that it's coming but that we are not quite there. It means overcoming a lot of challenges for us. I'll try to circle back to that article and lay out what we see as the challenges on the Linux side of life and why we haven't just made 64 bit support appear.
The idea of Supported Applications is a difficult topic. The truth is we have a core set of applications that we test on a bi-weekly basis (every time a new version of Wine is released). We use these applications to gauge the stability of Wine and lead our developers in what might need attention. We add and remove applications from this list for various reasons. Sometimes applications stay on the list even if they have a native version because they are so useful to test (like Portal or Team Fortress 2). Traditionally, this has been what we call "Support Applications".
Beyond that, we have an amazing team of people who volunteer their time and frankly get to our forums to answer questions for us before our staff can get there. People like Silviu, JP, Gary, and many more, too many to mention over the years. I live for these people and the help they give (that's why I started the page explaining why 64 bit support is difficult for us to simply turn on). They watch their favorite applications and the general functionality of CrossOver at all hours of the day and night. They create things like CrossTies that make applications easy to run and their advice is certainly more informed than ours when it comes to their favorite applications. These applications were not getting the "Supported" go ahead from us but were running at a gold status with community support that meant no additional effort from our staff (when something just runs, they definitely make us look good; when something needs a workaround, they write it, etc). We didn't want to downplay that designation anymore. We wanted to say their word is as good as ours for their favorite applications.
We removed the "Supported Application" designation from our website when we revamped it. An application works now based on our star system and we think it's more informative. I'm getting off topic... please read about our star rating system here.
Getting "better support from PlayOnLinux..." this is a hard piece to explain and realize. The truth is, the PlayOnLinux community is great, too. They do well in finding ways to run applications with Wine and make it easy for the end user. I don't want to downplay that or take away from that. PlayOnLinux benefits from the same work as CrossOver and all of the other third party applications that are based on Wine. The biggest distinction is, CodeWeavers is the corporate sponsor of Wine. We employ a large group of the Wine developers, including Alexandre Julliard. A breakdown of who is who for the Wine Project with CodeWeavers. When someone purchases CrossOver, they are helping fund additional work on Wine and helping do things like continue our support of the WineHQ website (it's on the front page of WineHQ, we host the site. Our system administrator does the skeletal work for WineHQ and then many others refine it).
As far as programs that don't run in CrossOver and including additional versions of Wine... as already alluded to, this is difficult for our Support and Testing teams (not to mention our developers). The reason is the nature of Linux, especially. There are so many different distributions and combinations therein. I could (for example) be running Ubuntu 64bit with Unity stripped out so I'm running XFCE and I'm running Nvidia drivers but I decided not to run the most current ones that the Software Center suggests, I'm running an older version that is stable for me. Or maybe I role with Arch Linux to keep everything on the edge. Or maybe I like Fedora 23, the beta preview... but I chose KDE instead of Gnome. That is a lot of moving parts. To add in all the combinations of Wine (each bi-weekly version, staging, stable, etc) is madness. Sheer madness. It's not that it can't be done, we've discussed making it so people could turn it on for individual bottles or in a specific build of CrossOver... but then how would we support it? How would we test it? How would we ensure that CrossOver works in all the combinations or at least most?
Which comes to the next piece. We are a small team. We have about thirty employees, half of them are Wine developers. Then we have a Support Team of two, a testing team of two, and around four developers who work directly on our product (for things like library dependencies, installation of CrossOver, working with OS X versions, adding 64bit support, etc). Each new feature takes time, development, testing. We have to choose which is most important to work on and do that. Then the next feature, then the next feature. CrossOver 15 has a complete overhaul of how installation works, a complete overhaul of a rating system, an overhaul of the Linux GUI, polish on how libraries work, and so much more. Basically, they have been busy, really busy. It isn't that we don't want to add more to CrossOver, it's a question of resources... and to have more... people have to buy CrossOver. A vicious cycle.
I want to say that yes, we read these threads and we take these suggestions seriously. I want you to know where your money is going and know that no one is getting rich off of people paying for Wine. I want you to know that we humbly appreciate the feedback and support of CodeWeavers and the Wine Community at large.