I've only scanned this thread, but think that there are some points of view that are being missed here. I am a retired electrical engineer whose professional duties did not require any schematic entry or any of the other tasks/tools associated with PC design. I therefore did not power up the learning curve on any of the high dollar packages. I did have hobby use for these activities and looked into a large number of cheap/free EDA packages, starting in the mid-90s with PADS. When Autotrax and then Dex came along they were the first ones that clicked for me, and I have used them for about ten years. That is not to deny it's warts. There are many. But it is very usable for hobby style design activities (Single or double sided boards with occasional 4 layer, varying density, up to about 4 inches by 8 inches and up to the low hundreds of components). I wouldn't feel bad recommending DEX to small shops whose primary activity is not pwb design. People who do schematic capture/PWB design full time or who routinely do boards with dozens of high pin count ICs would be well advised to get the tools from the big guys.
Many of the objections I have seen in the thread are due to differences in the UI from what the reviewer is used to. It is a little like someone saying that Photoshop is bad because is doesn't work the way GIMP does (or visa versa). Or that Excel is no good because it is different from Lotus 123.
What made it click for me might not be right for others. The following describes my situation and some of why it works for me so that others can see if it has any meaning to them. I have been doing one or two boards per year over the last decade. This means I go back up the learning curve for each board. Most of the GNU stuff requires a fairly complex workflow that I had trouble picking up so they were out. Eagle's interface was ok for me, but not great, and Eagle's free version is very limiting. Eagle gets pricey (in hobbiest terms) quickly as you add capability. None of other dozen or so free ones had an easy to learn interface. Everyone, pro or amateur fights parts modeling (well some of the pro's get to farm that out to another department). Even with Eagle's enormous library I was always needing to model my own parts (and still do now that DEX has imported the Eagle libraries). So the fact that the part modeling works pretty well for me is important. The only thing I usually have trouble with is generating a really sharp 3D view. Finally, I grew up with arc overs on schematics. I know it doesn't conform to today's standards, but my schematics are for my use and that is the way I want them.