| Having just switched from EAGLE to KiCad I think I'm qualified to offer an answer to that question. The short answer: it is better. If you are considering switching, do not wait, just switch. I should have done this sooner. The longer answer: Both tools have drawbacks and the user interface is bizarre in many ways in both of them. That said, KiCad at least is being regularly improved. I got tired of waiting for EAGLE to fix even the most ridiculous UI flaws. It seemed just as if EAGLE wasn't really developed anymore, just stuck way back in the 90s. My schematics look much better these days. Hierarchical sheets help, too. The separation of symbols from footprints is a great idea. As a practical example, I already have a small library of Texas Instruments packages (DRC, DRV, etc), which means that I can often just draw a symbol and immediately assign a verified footprint to it. No copying, and the footprints are shared, so if you modify paste coverage once, all parts using that footprint can immediately benefit. This idea is a clear winner. Routing boards takes significantly less time than in EAGLE. Mostly because of the push and shove router — I don't think I'd even take on some boards I'm making these days without it. The layers seem to be better organized: you don't get a hundred layers with weird names, the set is clearly defined and it's easy to understand what they are used for. 3D visualization is really great. I didn't think it would be useful, but I can't live without it these days. All the components in my libraries now have 3d models attached, even if the model is a simple cube. This helps greatly when designing small stuff that is supposed to go into real enclosures. Exporting to decent CAD packages isn't quite there yet (you can do it, but it requires significant effort), but the ability to instantly visualize your board helps a lot already. The library management is as bad as it was in EAGLE. Perhaps slightly better because you can use github repos as sources, but in general it's a crappy experience. I hope this will improve in the future. Finally, price is an important consideration. EAGLE is not free. If you do anything commercial, EAGLE suddenly starts to be quite expensive, especially if you want 4-layer boards or larger boards. Other commercial packages are even more expensive. So if you are a serious hobbyist who wants to produce small 4-layer boards at OSHpark, KiCad is really the best option. In general, I see no compelling reason to stick to EAGLE unless you have zero time for learning new things. |
The only thing I'd add is that anybody who's thinking of switching should treat it like picking up a new, very different programming language. It took me three weeks with several boards and a video tutorial series to finally get comfortable that I can use the tool without constantly looking up hotkeys and documentation (which is really good).
The thing I recommend is to never assume that the way KiCad is doing something is the only way, and to Google aggressively. A good example is the 'Move' tool vs the 'Grab' tool. I watched a guy nearly swear off KiCad because he only used Move and never Grab, so he was moving wire segments individually. If he'd read the documentation or searched for the answer, it would have been there. These tools are not particularly intuitive.
The best part of taking some dedicated time is that now I have 2-layer and 4-layer templates with my design rules, custom project settings, and a bunch of custom hotkeys. It makes all the difference.